← Back to context

Comment by trey-jones

6 years ago

I feel like the main response should be "OK, we'll just host our own Docker Registry."

This has been available as a docker image since the very beginning, which might not be good enough for everyone, but I think it will work for me and mine.

Agreed that self-hosting registries should be way more common than it is today and maybe even standard practice.

It's crazy easy to do; just start the registry container with a mapped volume and you're done.

Securing, adding auth/auth and properly configuring your registry for exposure to the public internet, though... The configuration for that is very poorly documented IMO.

EDIT: Glancing through the docs, they do seem to have improved on making this more approachable relatively recently. https://docs.docker.com/registry/deploying/

Note that for OSS images, that's a non-trivial thing to do—you have to have somewhere to run the image, and somewhere to store your images (e.g. S3), both of which are non-free, and would also require more documentation and less discoverability than Docker Hub offers.