Issue #1750
closed
Docker pull failing to function with docker pull setup
Description
Hi
I am currently working on trying to integrate pulp/crane setup into the in progress CentOS Community Container Pipeline story. I have been facing multiple issues from multiple fronts which I have been trying to solve. While trying to work with it, docker pull fails even though the registry has been published. I have collected all the information that I could and i will let it do the talking more that me.
I am using the pulp v 2.8 beta while doing this
Files
Even if i set it as --insecure-registry, I get most of the same logs minus the SSL stuff.
- Version changed from 2.7.1 to Master
Hello Mohammed,
It seems that you only have Docker v1 data in your repository (the Image is the v1 unit). It looks like you have the Docker client configured to try to pull from your repository first, and then go to the Docker registry. Additionally, it seems that it tries the v2 protocol on your repository (which rightfully 404's since you don't have any Docker Manifests/Tags/Blobs) and then falls back to v2 on the Docker registry, and then falls back to v1 on the Docker registry. It does not seem to ever attempt v1 on your registry. There is not much we can do about that since this is the Docker client itself.
One thing you might try is being more explicit with your docker pull command. Perhaps a "docker pull <host:port>:pulpdemobox would get the client to try v1 on your registry after v2?
P.S. In the future, could you include the text in the description and comments here instead of using attachments? It's easier for others to find when they search, and it's easier for us to read too. That is, unless it's huge ☺
I will see if i can find a mechanism that spits out v2 images to push. As far as i know upto docker 1.9, docker save produces v1 tarballs
- Status changed from NEW to CLOSED - NOTABUG
Hello again!
You are correct - docker save can only be used to get Docker v1 content into Pulp. To get Docker v2 content into Pulp, you must synchronize Pulp with a registry that has the content you want. Thus, if you want to use Pulp to manage custom content, you will need to run a Docker registry, push your Manifests/Blobs into it, and then point Pulp's feed URL at it and sync. I hope that helps!
I'm going to close this bug for now. If you experience further issues, feel free to reopen or file a new issue. Thanks for the report!
We are removing the 'API' category per open floor discussion June 16, 2020.
Also available in: Atom
PDF
.