From 204d4b43a7b25855553cf6a04a6fa71b8f19f8ee Mon Sep 17 00:00:00 2001 From: jlafleche Date: Fri, 15 Jul 2022 22:59:09 +0800 Subject: [PATCH] clarify push manifest spec Signed-off-by: jlafleche --- spec.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/spec.md b/spec.md index 297e2745..26632666 100644 --- a/spec.md +++ b/spec.md @@ -423,6 +423,8 @@ Manifest byte stream: The uploaded manifest MUST reference any blobs that make up the artifact. However, the list of blobs MAY be empty. + +The registry MUST store the manifest in the exact byte representation provided by the client. Upon a successful upload, the registry MUST return response code `201 Created`, and MUST have the following header: ``` @@ -430,6 +432,8 @@ Location: ``` The `` is a pullable manifest URL. +The Docker-Content-Digest header returns the canonical digest of the uploaded blob, and MUST be equal to the client provided digest. +Clients MAY ignore the value but if it is used, the client SHOULD verify the value against the uploaded blob data. An attempt to pull a nonexistent repository MUST return response code `404 Not Found`.