From 19e5fa571c14f0ce0dbd434c5196870f2c0092f6 Mon Sep 17 00:00:00 2001 From: Brandon Mitchell Date: Thu, 8 Sep 2022 13:55:54 -0400 Subject: [PATCH] Registries MUST accept refers to unknown manifests Signed-off-by: Brandon Mitchell --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index 605981c5..234e5ec9 100644 --- a/spec.md +++ b/spec.md @@ -209,7 +209,7 @@ Pushing an object typically works in the opposite order as a pull: the blobs mak 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 a manifest of any type uploaded to the manifest endpoint if it references manifests or blobs that do not exist in the registry. -A registry SHOULD accept a manifest with a `refers` field that references a manifest that does not exist. +A registry MUST accept an otherwise valid manifest with a `refers` field that references a manifest that does not exist, allowing clients to push a manifest and referrers to that manifest in either order. When a manifest is rejected for these reasons, it MUST result in one or more `MANIFEST_BLOB_UNKNOWN` errors [code-1](#error-codes). ##### Pushing blobs