Skip to content

Registries MUST accept refers to unknown manifests#341

Merged
sudo-bmitch merged 1 commit intoopencontainers:mainfrom
sudo-bmitch:pr-refers-must-accept
Sep 14, 2022
Merged

Registries MUST accept refers to unknown manifests#341
sudo-bmitch merged 1 commit intoopencontainers:mainfrom
sudo-bmitch:pr-refers-must-accept

Conversation

@sudo-bmitch
Copy link
Copy Markdown
Contributor

Resolves #340

Signed-off-by: Brandon Mitchell git@bmitch.net

@sudo-bmitch sudo-bmitch added this to the v1.1.0 milestone Sep 8, 2022
Signed-off-by: Brandon Mitchell <git@bmitch.net>
@sudo-bmitch sudo-bmitch force-pushed the pr-refers-must-accept branch from de74b0f to 19e5fa5 Compare September 8, 2022 23:48
Copy link
Copy Markdown
Member

@mikebrow mikebrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM...

noting here that this MUST requirement does not mean the registry can't garbage collect manifests such as these with a refers digest reference that either no longer or never existed in the registry..

@sudo-bmitch sudo-bmitch merged commit b5e110d into opencontainers:main Sep 14, 2022
@sudo-bmitch sudo-bmitch deleted the pr-refers-must-accept branch September 14, 2022 09:43
@jdolitsky jdolitsky mentioned this pull request Sep 15, 2022
@sudo-bmitch sudo-bmitch mentioned this pull request Feb 1, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Vote] Should manifests with a refers field that points to something that doesn't exist in the repository be accepted by a registry?

5 participants