Project

Profile

Help

Issue #1893

closed

pulp_docker does not support Docker < 1.10 with manifests that were published from Docker >= 1.10

Added by rbarlow over 8 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Crane:
Platform Release:
2.8.7
Target Release - Crane:
2.0.3
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 4
Quarter:

Description

Tim Waugh reported this issue, so I will use the text he wrote up here:

The V2 manifest that Docker 1.10 pushes to the Distribution registry, and which will get synced into Pulp, is Schema 2, which Docker 1.9 does not understand. When Docker engine 1.9 pulls from a Distribution registry, Distribution sees that it is talking to a client that does not understand Schema 2, and converts the manifest to Schema 1 before sending its response.

This means there are effectively three things:

    V1, supported by all Docker engine versions
    V2 (Schema 1), supported by 1.6 up to 1.9
    V2 (Schema 2), only supported by 1.10

In order for Pulp to be able to satisfy both 1.6 – 1.9 clients and 1.10 clients, it will have to learn to convert Schema 2 manifests to Schema 1 manifests.

https://github.com/docker/distribution/blob/master/docs/compatibility.md#manifest-push-with-docker-110
https://gist.github.com/aaronlehmann/b42a2eaf633fc949f93b#interoperability-with-old-image-formats

Related issues

Related to Packaging - Task #2083: Issues common to 2.9.1 and 2.8 streamCLOSED - NOTABUGsemyers

Actions

Also available in: Atom PDF