Re:Docker registry is hard-coded and other registry is a sec...
by yebyen on Tuesday June 24, 2014 @12:20PM
(#7938571)
yeah, that seems to be the thread here...
git has this concept of "remotes" which can be defined per project, but Docker has no such concept of a remote or even of a project. You have a Dockerfile and you have an image.
To be fair, there should be some kind of an "enterprisey" caching proxy that enables IT departments to act as a supervisor or man-in-the-middle, blessing some trusted images and forbidding the downloading of others, holding any pushes in a queue for "public release approval."
The docker-registry open source tool is rudimentary. I think there will certainly be alternatives to index.docker.io, and eventually even a configuration directive to select a different image host as the default.
git has this concept of "remotes" which can be defined per project, but Docker has no such concept of a remote or even of a project. You have a Dockerfile and you have an image.
To be fair, there should be some kind of an "enterprisey" caching proxy that enables IT departments to act as a supervisor or man-in-the-middle, blessing some trusted images and forbidding the downloading of others, holding any pushes in a queue for "public release approval."
The docker-registry open source tool is rudimentary. I think there will certainly be alternatives to index.docker.io, and eventually even a configuration directive to select a different image host as the default.