Open garystafford opened 9 years ago
+1. docker registry push/pull also works locally for me but when deployed on ECS I'm seeing the same error. I'm tunneling in though ssh so the push/pull is still to localhost, but just to be safe I'm using --insecure-registry localhost:5000
in my boot2docker docker config. other docker containers on the same server can send and receive network requests through a similar ssh pipe so it seems like it's not a connectivity issue. any advice would be appreciated
@garystafford the VM is a different host. You cannot expect "localhost" from machine A to be "localhost" for machine B. So, if you start your registry on machine A, with ip X.Y.Z.W, use X.Y.Z.W instead of localhost to pull images from.
@evanbeard same thing, likely. Expecting localhost to resolve to a remote machine is unrealistic.
Hope that helps.
I have create a local registry at localhost:8950 (5000 was in use). I can push and pull images to it without issue. However, once I spin up a VirtualBox VM with Docker Machine, and switch to that environment, I can no longer pull images from the repository. Is the expectation that these two applications work together? The localhost, single host scenario is the simplest test case I could create. Assuming repository is still considered 'local' to Docker Machine VM?
From with the Docker-Machine environment, when I run my docker-compose up command, I get:
Even a direct docker pull commands get an error:
I have confirmed it works locally, outside the docker machine environments, by pulling and pushing images. The container is running fine: