-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: Adding a local docker registry in the vagrant box #16
Comments
I believe the plan was to find a way to integrate a build / render service for the layered images and couple that with the registry / delivery mechanism. If we can, I would recommend we hold off implementing the registry / delivery plan before we have clarity on the build/render process as well. This is something we should definitely have ( maybe hooked in via a CI process as well ). |
As discussed with @whitel and @kbsingh
This is not the registry we need to expose but just for dev/local-test |
As discussed, adding the docker-registry to the vagrant box. |
A couple comments: 1) should we warn the user that a vagrant destroy will blow away the contents of the registry the user added? or is that obvious? 2) we should open another ticket for the registry-ui. |
@whitel Yeah, we need to work on the documentation for this |
Was thinking it might be nice to ship this vm with a running docker registry (and/or docker-registry-ui ) either direct or in kube. I know I always end up needing one to work on atomicapps, but I think it is arguable.
The text was updated successfully, but these errors were encountered: