Issue #1685: index.docker.io seems to support the v2 API, contrary to what our dockermentation states - Docker Support - Pulp

Actions

Send by e-mail Copy link

Issue #1685

closed

index.docker.io seems to support the v2 API, contrary to what our dockermentation states

Added by rbarlow almost 9 years ago. Updated over 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

amacdona@redhat.com

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version - Docker:

Platform Release:

Target Release - Docker:

2.0.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Documentation, Pulp 2

Sprint:

Quarter:

Description

When we were implementing v2 support against Dockerhub, it was determined that index.docker.io didn't support v2 even though it said it did. Thus we dockermented in many places that users should use a different endpoint. We also dockermented that they should use the --enable-v1 and --enable-v2 flags in various ways, depending on which endpoints they are using.

Now it seems that index.docker.io supports v2, so we need to revisit our dockermentation and fix it to be correct with the current state of affairs.

Actions

Copy link

Updated by rbarlow almost 9 years ago

Humorously, it seems that if you try to sync v1 content from index.docker.io, it now redirects you to registry-1.docker.io, which is the host that our docs say to use to get v2 content and did not do v1 at all before.

The good news is that it seems that users can just point their feed at index.docker.io and use the --enable-v{1,2} flags to get the behavior they want. So I think we can just drop all the warnings about feed URLs and what not and just focus on the --enable-v{1,2} flags.

Actions

Copy link

Updated by amacdona@redhat.com almost 9 years ago

Status changed from NEW to ASSIGNED
Assignee set to amacdona@redhat.com

Actions

Copy link

Updated by mhrivnak almost 9 years ago

Triaged changed from No to Yes

Actions

Copy link

Updated by amacdona@redhat.com over 8 years ago

Status changed from ASSIGNED to POST

index.docker.io was updated and now can forward requests for v2 content. However, this entire endpoint is deprecated and is likely to be removed relatively soon. Until it is removed, it is correct to sync v1 content from this endpoint, but it would not be a good choice to sync v2 content from the endpoint, even though it does work for the time being.

This is pretty much a NOOP, but I added a small note about the endpoint being deprecated.

https://github.com/pulp/pulp_docker/pull/139