-
Notifications
You must be signed in to change notification settings - Fork 392
404 Client Error: Not Found ("No such image: a") #564
Comments
Looks like possibly the failure is coming from this particular role because of
|
Yeah, it seems we need to ensure As far as the 404 error, I'd love to get a copy of |
Here are the
And here is the actual output of the
|
Using
|
@mrlesmithjr I've seen other users report this issue (and was even able to replicate it myself) who install [1] https://docs.ansible.com/ansible-container/installation.html#running-from-source |
@ehelms Good information to know. Hopefully this can get sorted out soon. |
So it looks like
|
I seem to experience the same issue with 0.9.1 Base OS/build env: Centos 7
container.yml
docker events
Commands used for building
requirements.txt
Output:
I also tried to clear /var/lib/docker folder. Also tried to build with root user directly in shell. Result is same. |
Okay! Mystery solved, methinks... The error about missing image 'a' comes from this section in docker-py: https://github.com/docker/docker-py/blob/e4093ab/docker/models/images.py#L176-L182 It's trying to identify when the build has finished properly so that it can return the image object. Unfortunately, the output of This is already documented as docker/docker-py#1625, which means it should be fixed in the next release of docker-py. |
I'm going to leave this open to track the |
Oh nice, good find man. |
The feedback on this is great and awesome find @j00bar .. So what's the workaround for now? I received the following
After only running |
@ehelms pointed out earlier in this issue that installing Ansible-Container from the source code on GitHub is the short-term solution. Refer to this link for the GitHub installation steps: https://docs.ansible.com/ansible-container/installation.html#running-from-source. This is no longer an issue in the 0.92rc0 release which should have a full/stable release soon. I have been using a virtual Python environment to run Ansible-Container from GitHub and can confirm that I no longer run into the issue. |
As a short-term fix, I applied the following patch in my build container to get around the 404 issue. |
This is bad for the project because the example in the documentation (i.e. |
Given how many people this is affecting, I've got a workaround that just needs testing. By ensuring the pip output for "Successfully built" begins with a package whose name does not begin with |
The reason it works with the |
It looks like the docker-py fix for this was released on July 28 https://github.com/docker/docker-py/milestone/33 We'll need to test, but once we do bumping the docker-py version in requirements.txt should resolve this. |
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
https://gist.github.com/mrlesmithjr/1e0f29b10d49c8f8bb0f001aef109c31
The text was updated successfully, but these errors were encountered: