From af7a3c14f89ecd5233dcb3d897c2d62e1723769e Mon Sep 17 00:00:00 2001 From: James Hewitt Date: Thu, 25 Nov 2021 11:49:44 +0000 Subject: [PATCH] Allow for rejection of image indexes with missing references Be more specific for missing references in the case of image indexes and not just image manifests. Signed-off-by: James Hewitt --- spec.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/spec.md b/spec.md index 3a96ee42..9449ed01 100644 --- a/spec.md +++ b/spec.md @@ -190,9 +190,12 @@ If the blob or manifest is not found in the registry, the response code MUST be #### Push Pushing an artifact typically works in the opposite order as a pull: the blobs making up the artifact are uploaded first, -and the manifest last. Strictly speaking, content can be uploaded to the registry in any order, but a registry MAY reject -a manifest if it references blobs that are not yet uploaded, resulting in a `BLOB_UNKNOWN` error [code-1](#error-codes). -A useful diagram is provided [here](https://github.com/google/go-containerregistry/tree/d7f8d06c87ed209507dd5f2d723267fe35b38a9f/pkg/v1/remote#anatomy-of-an-image-upload). +and the manifest last. A useful diagram is provided [here](https://github.com/google/go-containerregistry/tree/d7f8d06c87ed209507dd5f2d723267fe35b38a9f/pkg/v1/remote#anatomy-of-an-image-upload). + +A registry MAY reject an image manifest if it references blobs that are not yet uploaded, resulting in a `BLOB_UNKNOWN` error [code-1](#error-codes). + +A registry MAY reject an image index if it references digests that are not yet uploaded, resulting in a `MANIFEST_BLOB_UNKNOWN` error [code-5](#error-codes). + ##### Pushing blobs