Project

Profile

Help

Actions
Send by e-mail Copy link

Story #1454

closed

As a user, I can sync v2 content from docker hub

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:
% Done:

100%

Estimated time:
Platform Release:
Target Release - Docker:
2.0.0
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix, Pulp 2
Sprint:
Quarter:

Description

Currently Pulp does not receive an HTTP 200 when accessing https://index.docker.io/v2/. It is believed that there is a header we can supply with our request that will allow us to access the registry via the v2 protocol. We should learn what that header is and supply it when trying to use /v2/ content.

Related issues

Related to Docker Support - Issue #1598: clarify docs that index.docker.io only supported for v1CLOSED - CURRENTRELEASEipanova@redhat.comActions
Related to Docker Support - Issue #1596: Set docker v1 to off by defaultCLOSED - CURRENTRELEASEamacdona@redhat.comActions
Related to Docker Support - Issue #1404: Sync from un-namespaced V2 repository failsCLOSED - CURRENTRELEASEamacdona@redhat.comActions
Blocked by Docker Support - Story #1144: As a user, I can sync from a v2 registry that requires RFC7235 authorization headersCLOSED - CURRENTRELEASEamacdona@redhat.com

Actions
Actions
Send by e-mail Copy link

Also available in: Atom PDF