Project

Profile

Help

Issue #1750

closed

Docker pull failing to function with docker pull setup

Added by mohammed.zee1000@gmail.com about 8 years ago. Updated almost 4 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
CentOS 7
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

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

Pulp Admin (343 Bytes) Pulp Admin Pulp admin successfully shows the presence of the repository. mohammed.zee1000@gmail.com, 03/07/2016 11:18 AM
System Info (2.46 KB) System Info mohammed.zee1000@gmail.com, 03/07/2016 11:18 AM
imagename.json_data (680 Bytes) imagename.json_data The json files published by pulp for consumption by crane mohammed.zee1000@gmail.com, 03/07/2016 11:18 AM
Crane data_dir is v2 (4.56 KB) Crane data_dir is v2 Contains logs collected when cranes data_dir was looking up v1/app from pulp mohammed.zee1000@gmail.com, 03/07/2016 11:18 AM
crane data_dir is v1 (4.17 KB) crane data_dir is v1 Contains logs collected when cranes data)dir was looking up v2 /app from pulp mohammed.zee1000@gmail.com, 03/07/2016 11:18 AM
Actions #1

Updated by mohammed.zee1000@gmail.com about 8 years ago

Even if i set it as --insecure-registry, I get most of the same logs minus the SSL stuff.

Actions #2

Updated by rbarlow about 8 years ago

  • 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 ☺

Actions #3

Updated by mohammed.zee1000@gmail.com about 8 years ago

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

Actions #4

Updated by rbarlow about 8 years ago

  • 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!

Actions #5

Updated by bmbouter almost 5 years ago

  • Tags Pulp 2 added
Actions #6

Updated by bmbouter almost 4 years ago

  • Category deleted (14)

We are removing the 'API' category per open floor discussion June 16, 2020.

Also available in: Atom PDF