New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't pull openshift/busybox-http-app #15699
Comments
Can you provide your docker daemon logs? (preferably ran in debug with -D) |
|
@exarkun this is not complete daemon logs unfortunately. |
It's the log from the relevant time period. I'll post a complete log now if that's what you want. |
@exarkun there is necessarily something after "Trying to pull". |
Here's the
|
I would have thought so as well. It doesn't appear as though anything related ever shows up, though. |
@exarkun these are not the daemon logs. |
Bit confused as well; I noticed that in your original description, calls are made to the v1.19 API, but your later logs are to v1.15? Or is that another API?
|
@dmp42 I repro'd this on IRC this morning against master + curl root@29c929ffd969:/go/src/github.com/docker/docker# curl -XPOST localhost/images/create?fromImage=openshift/busybox-http-app
DEBU[0002] Calling POST /images/create
INFO[0002] POST /images/create?fromImage=openshift/busybox-http-app
DEBU[0002] Trying to pull openshift/busybox-http-app from https://registry-1.docker.io v2
{"status":"Status: Image is up to date for openshift/busybox-http-app"}
root@29c929ffd969:/go/src/github.com/docker/docker# curl localhost/images/json?all=1
DEBU[0038] Calling GET /images/json
INFO[0038] GET /images/json
[] Adding the :latest tag works as expected. |
Note that I can do |
Looks like this has to be reported to https://support.docker.com then, perhaps they can check what's different with this repo? |
@dmp42 Are you saying that what I put in the gist is not the docker daemon logs? The lines "Daemon has completed initialization" and "Docker daemon" that appear in it seemed like strong suggestions to me that that's what it was. I took this from /var/log/upstart/docker.log on an Ubuntu system. If the daemon logs somewhere else, can you tell me where that is? Thanks!
@thaJeztah Sorry about that. I tried with different API versions to see if that made a difference and I observed the same behavior which each version I tried. I was sloppy w/ the reporting and didn't make this clear.
Okay, I'll do that. Thanks. |
Thanks! Please keep us posted if they found something |
Tested this on a new AWS Ubuntu instance:
Python test script I used (This fails):
Changing the image_name line to: Daemon log:
pulling directly from command line works: |
The issue seems to have been resolved, perhaps by a change to Docker Hub? |
Hmmm, I get this with every attempt to run applications using the openshift alpha all-in-one vm, eg:
same with attempting to get an ubuntu image. (oc new-app ubuntu, which I know will fail on startup). |
@ianmiell sounds like an issue that needs to be reported at openshift? |
oops, that's where I thought i'd landed! |
@ianmiell haha, no problem 😄 |
Let me close this ticket for now, as it looks like it went stale. |
When I try to pull this image, the Docker daemon reports it is up to date. When I try to run a container using this image, the Docker daemon reports the image doesn't exist. This happens every time I try the simple program attached (see below).
If I replace the image name with `openshift/busybox-http-app:latest" the problem seems to go away.
Here's a transcript of an interaction between the Docker daemon and a Python (docker-py-using) program that does a pull and a create:
I can reproduce this on Ubuntu 14.04 and CentOS 7 on AWS using Docker 1.8.1 from get.docker.com.
Ubuntu details:
docker version
:docker info
:uname -a
:Running on AWS using ami-5189a661
Reproducer:
The output of this program when I run it is:
Instead, I expect the
latest
tag of the image to be pulled and then used to run a new container.The text was updated successfully, but these errors were encountered: