You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a bridge too far, but, as long as I'm spitballing...
Would it be useful when NeuroDocker is asked to build a container, it checks with known container repositories (ReproNim/containers, for example) to see if that same container has been built already, and if so, recommends that the user consider using that one, as opposed to creating an additional identical version of the container?
If an identical one is not known, would it be useful when NeuroDocker builds a container, to offer an option to contribute it to ReproNim/containers?
The text was updated successfully, but these errors were encountered:
This might be a bridge too far, but, as long as I'm spitballing...
Would it be useful when NeuroDocker is asked to build a container, it checks with known container repositories (ReproNim/containers, for example) to see if that same container has been built already, and if so, recommends that the user consider using that one, as opposed to creating an additional identical version of the container?
If an identical one is not known, would it be useful when NeuroDocker builds a container, to offer an option to contribute it to ReproNim/containers?
The text was updated successfully, but these errors were encountered: