Actions
Story #1454
closed
As a user, I can sync v2 content from docker hub
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
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
Updated by amacdona@redhat.com almost 9 years ago
- Subject changed from As a user, I can sync v2 content from index.docker.io to As a user, I can sync v2 content from docker hub
Updated by amacdona@redhat.com almost 9 years ago
- Related to Issue #1598: clarify docs that index.docker.io only supported for v1 added
Updated by amacdona@redhat.com almost 9 years ago
- Related to Issue #1596: Set docker v1 to off by default added
Updated by amacdona@redhat.com almost 9 years ago
- Related to Issue #1404: Sync from un-namespaced V2 repository fails added
Updated by amacdona@redhat.com almost 9 years ago
- Blocked by Story #1144: As a user, I can sync from a v2 registry that requires RFC7235 authorization headers added
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
With the completion of https://pulp.plan.io/issues/1144, this story is complete.
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from MODIFIED to 5
Updated by semyers over 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
.