4 ms·
I thought they didn't make private registries available because it would "fragment the ecosystem" Here's the conversation I saw: https://stackoverflow.com/que
by m463 6y ago
I thought they didn't make private registries available because it would "fragment the ecosystem"
Here's the conversation I saw:
https://stackoverflow.com/questions/33054369/how-to-change-the-default-docker-registry-from-docker-io-to-my-private-registry https://stackoverflow.com/questions/33054369/how-to-change-t...
pointing to this:
https://github.com/moby/moby/issues/7203 https://github.com/moby/moby/issues/7203
and also there was this comment:
"It turns out this is actually possible, but not using the genuine Docker CE or EE version.
You can either use Red Hat's fork of docker with the '--add-registry' flag or you can build docker from source yourself with registry/config.go modified to use your own hard-coded default registry namespace/index."
- justincormack 6y agoNo you have misunderstood the issue. You can use any registry, just write out the domain for it, this has always worked and is very widely used. Red Hat changed the default if you don't specify a FQDN, before they decided not to ship Docker at all.
- m463 6y agoI understand that point, but it makes it harder to not "accidentally" pull from a public registry with intertwined docker images (which most people use)