Getting 404 (image not found) when trying /v1/images/<image name>/ancestry #130
Comments
Related issue: moby/moby#2461 |
Hi @vmalloc, Could please certify that your local time is synced? Thanks |
We're using ntp. From what I can tell both machines are synced. — On Thu, Nov 28, 2013 at 2:06 AM, Roberto Gandolfo Hashioka
|
I noticed this recently and dug into it. My |
I'm getting the same error. I have started the registry with:
The config file looks like:
I then pull an image from the index:
And tag it as follows
When push is being performed I see the following on the server
On the client I see
When I try and pull this image I get the following error:
And in the registry I see
When I browse to the images directory of the registry I see the following entries
docker version gives the following output
|
I am having a similar problem using the registry container on the Docker index. I was able to work around it by updating the git repo in the container to the latest. docker run -e DOCKER_REGISTRY_CONFIG=/registry/config.yml -p 5000:5000 -v /opt/registry:/registry -m 0 registry /bin/sh -c 'cd /docker-registry && git remote add origin https://github.com/dotcloud/docker-registry.git && git pull origin master && ./setup-configs.sh && exec ./run.sh' The documentation suggests that the "preferred" way of running a private registry is to use the registry container in the docker index, but the fact that:
suggests that the registry container still needs some work. |
cc @shin- |
Yup, same for me, the official image seems to be out of date. As soon as I run the latest from the repo everything seems to work perfectly again. Happy to help out in anyway I can, getting this thing running against a CI server like Travis or something. |
This doesn't happen consistently, but sometimes
docker pull
decides to request this path and stumbles upon 404 (and fails as a result).Could this be a docker issue? Is it related to docker-registry?
Thanks in advance
The text was updated successfully, but these errors were encountered: