Project

Profile

Help

Story #1050

closed

As a user, I can "docker pull" using the v2 API

Added by mhrivnak almost 9 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Target Release - Crane:
2.0.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Quarter:

Description

Crane must implement the "docker pull" v2 API. This includes:

GET /v2/

must return 200 and the custom "Docker-Distribution-API-Version" header with value "registry/2.0".

GET /v2/<name>/<path>

must redirect to the corresponding base URL defined for the <name> joined with the relative <path>.

The "redirect files" that crane uses to load data about repositories has been updated for docker V2. The schema for this data file has been bumped to "2", with details here: https://github.com/pulp/pulp_docker/blob/docker_v2_api/docs/tech-reference/distributor.rst#v2-redirect-file

It may be easiest to store these in a new in-memory data structure. So when loading data files, if it is a V1 file keep the current behavior, and if it's a V2 file add the data to a new but similar structure. Then they can be accessed separately by request handlers for /v1 and /v2. In theory, one repo could have content both under /v1 and /v2.

To facilitate easier organization of v1 vs. v2 data files, it is important that crane be able to load them from anywhere within its configured data_dir. So it should look for all json blobs within that directory and any subdirectories, and load them as data files.

Reference: https://github.com/docker/distribution/blob/master/docs/spec/api.md


Related issues

Related to Crane - Story #1049: Add v2 concepts to data file schemaCLOSED - CURRENTRELEASErbarlow

Actions
Blocks Docker Support - Task #1048: Tracker for Docker v2 API and Manifest workCLOSED - CURRENTRELEASErbarlow

Actions

Also available in: Atom PDF