Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Docker private registry has confusing "library" subfolder
-
Q1. What is the "/library" subfolder used for? when is it necessary to include it?
Q2. Why can I "docker pull/push" an image with the "/libary" and without the "/library" subfolder?
I find this confusing, because if I push/pull with & without the subfolder, then I have a duplicate image in the "docker image ls" list.
Reference: Indeo docs https://docs.inedo.com/docs/proget/docker/private-registries; the "/library" subfolder is introduced in the API syntax under the Deleting Images section; for instance: https://proget.example.com/v2/main/**library**/node/tags/list, https://proget.example.com/v2/main/**library**/node/manifests/latest. -
Welcome to Docker ;)
In Dockerland, all container image repositories (i.e. "folders") must be in a namespace.
libraryis a reserved namespace, and it's synonymous with with_and(empty). This means, when you do something like ,docker pull ubuntu, the client will translate that tolibrary/ubuntu, then request it from the registry. Same thing with push.You should avoid using
library(or(empty)namespaces) for your own container images. Just put your own company name in.FYI, we have some big plans with making this a lot easier to work with in the future, stay tuned!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login