[FEATURE] : Add a config entry for docker push to point to a private registry.

[shankarj]

After a long dig, I read in the documentation,

[UPDATE] : This is to "completely" implement a private registry. docker push and pull both pointing to a local registry. Thank you @unclejack for the clear explanation.

"It’s important to note that we’re using a domain containing a “.” here, i.e. localhost.domain. Docker looks for either a “.” (domain separator) or “:” (port separator) to learn that the first part of the repository name is a location and not a user name. If you just had localhost without either .localdomain or :5000 (either one would do) then Docker would believe that localhost is a username, as in localhost/ubuntu or samalba/hipache. It would then try to push to the default Central Registry. Having a dot or colon in the first part tells Docker that this name contains a hostname and that it should push to your specified location instead."

FEATURE : It would be great if by default, docker push could push to a private registry defined in the config file. If no private registry is set up, then docker could push to the main registry. This would really reduce the effort needed to tag images with the FQDN all the time.

[unclejack]

@shankarj What you're asking for would break the global namespace.

Your Docker installation with this "private registry defined in the config file" would be incompatible with every other Docker installation out there. Running docker pull debian needs to pull from the same place on every Docker install.

A developer using Docker on their box will use debian, centos and ubuntu official images. Your hacked up Docker install would just serve your own versions of those images (if they're present) and this will break things.

You'll discover that this has been discussed already and that there's no intention to change this. Please don't open more issues on this topic because this isn't going to be implemented.