From aa6e69711a1617e207cc659a2b1fc689f99991ce Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Thu, 24 Aug 2017 07:29:19 +0800 Subject: [PATCH] Update compatibility.md (#4321) --- docs/compatibility.md | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/docs/compatibility.md b/docs/compatibility.md index 6e04dee4d..90cef416c 100644 --- a/docs/compatibility.md +++ b/docs/compatibility.md @@ -9,7 +9,7 @@ title: Registry compatibility and older, and the manifest was pushed with Docker Engine 1.10, a security check will cause the Engine to receive a manifest it cannot use and the pull will fail.* -## Registry Manifest Support +## Registry manifest support Historically, the registry has supported a [single manifest type](./spec/manifest-v2-1.md) known as _Schema 1_. @@ -21,7 +21,7 @@ with older Docker engines will, in certain cases, do an on-the-fly transformation of a manifest before serving the JSON in the response. This conversion has some implications for pulling manifests by digest and this -document enumerate these implications. +document enumerates these implications. ## Content Addressable Storage (CAS) @@ -45,15 +45,7 @@ support the new version. ## Registry v2.3 -### Manifest Push with Docker 1.9 and Older - -The Docker Engine will construct a _Schema 1_ manifest which the -registry will persist to disk. - -When the manifest is pulled by digest or tag with any docker version, a -_Schema 1_ manifest will be returned. - -### Manifest Push with Docker 1.10 +### Manifest push with Docker 1.10 The docker engine will construct a _Schema 2_ manifest which the registry will persist to disk. @@ -75,3 +67,12 @@ For this reason if a manifest is pulled by _digest_ from a registry 2.3 with Doc Engine 1.9 and older, and the manifest was pushed with Docker Engine 1.10, a security check will cause the Engine to receive a manifest it cannot use and the pull will fail. + +### Manifest push with Docker 1.9 and older + +The Docker Engine will construct a _Schema 1_ manifest which the +registry will persist to disk. + +When the manifest is pulled by digest or tag with any docker version, a +_Schema 1_ manifest will be returned. +