Details for posterity: since porting CM to Docker, the local registry that is launched in dev mode can no longer be referred to by hostname. While it can be resolved internally, Docker operations that interact with the registry (e.g. pull) will no longer work, since that happens externally through the Docker Remote API. To avoid the extra step of adding an entry to /etc/hosts and equivalent, this PR makes it so that the dev mode registry is referenced as localhost:5000 rather than databox-local-registry:5000.
One more point to note is that because of all this, databox-cloud-net no longer serves any purpose (though might later says @Toshbrown) since the registry was the only component that needed it, and with these changes, the registry doesn't need to be connected to anything internally, since any interaction with it happens behind the Docker socket.
Details for posterity: since porting CM to Docker, the local registry that is launched in dev mode can no longer be referred to by hostname. While it can be resolved internally, Docker operations that interact with the registry (e.g. pull) will no longer work, since that happens externally through the Docker Remote API. To avoid the extra step of adding an entry to
/etc/hostsand equivalent, this PR makes it so that the dev mode registry is referenced aslocalhost:5000rather thandatabox-local-registry:5000.One more point to note is that because of all this,
databox-cloud-netno longer serves any purpose (though might later says @Toshbrown) since the registry was the only component that needed it, and with these changes, the registry doesn't need to be connected to anything internally, since any interaction with it happens behind the Docker socket.