Proposal J - new media type for compatibilities with update in image … #20
Conversation
ChaoyiHuang
requested review from
mfranczy,
vsoch,
sudo-bmitch,
cyphar and
neersighted
as code owners
…index platform This proposal is born from proposal A to I, providing another option to hold compatibilities, and retriving the compatibilities in shorter path. The purpose of the proposal, based on the maintainers feedback, is to address the concern maintaining a standalone artifact specification in OCI. Signed-off-by: joehuang <[email protected]>
|
|
||
| ### add platform.compat descriptor | ||
|
|
||
| Add a new descriptor in platform object in [image index](https://github.com/opencontainers/image-spec/blob/main/image-index.md#image-index-property-descriptions). |
There was a problem hiding this comment.
I have concerns that this descriptor would not be known to existing registries and client tooling. As a result, registries would accept an incomplete manifest, or silently delete the compatibility blob in a later GC cycle. And client tooling to copy images would fail to include the compatibility blobs.
There was a problem hiding this comment.
yes, this is the risk. some experiments need to be done to investigate the result of unknown descriptor
There was a problem hiding this comment.
@sudo-bmitch is right, so far I confirmed that with regclient and zot registry.
For this proposal we would have to add a descriptor and a new media type support to regclient and zot.
Didn't test other registries and tools yet.
new media type for compatibilities with update in image index platform
This proposal is born from proposal A to I, providing another option to hold compatibilities, and retriving the compatibilities in shorter path.
The purpose of the proposal, based on the maintainers feedback, is to address the concern maintaining a standalone artifact specification in OCI.