New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support OCI Artifact Manifests #3833
Support OCI Artifact Manifests #3833
Conversation
Does not yet make referrers link from the subject to the referrer Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Subjects of referrers should link back to those referrers Signed-off-by: Bracken Dawson <abdawson@gmail.com>
So that one can easily tell if it was not set or was set invalidly. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
When an artifact is uploaded link its subject back to the artifact, even if the subject does not exist yet. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Future non-OCI artifacts would not be able to live in the same package Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Deletion already works. Referrers links are left dangling so that deletions don't have to try to parse the content. The artifact listing API will need to validate each artifact and GC may want to clean up dangling referrer links. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
If a manifest which cannot refer to a subject has a subject field then we should ignore that field and not make a referrer link on that subject. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
It may likely be needed by garbage collect later. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
Signed-off-by: Bracken Dawson <abdawson@gmail.com>
We do no know that we were handling a PUT request here. Signed-off-by: Bracken Dawson <abdawson@gmail.com>
de1cb46
to
38900e0
Compare
Codecov ReportBase: 56.56% // Head: 56.62% // Increases project coverage by
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #3833 +/- ##
==========================================
+ Coverage 56.56% 56.62% +0.06%
==========================================
Files 105 107 +2
Lines 10638 10751 +113
==========================================
+ Hits 6017 6088 +71
- Misses 3948 3985 +37
- Partials 673 678 +5
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to put this on hold until opencontainers/image-spec#999 is resolved
Hello @milosgajdos @brackendawson Will this PR permit attaching some artefact to an OCI image on DockerHub with tools like oras attach, for example? i say that because Dockerhub is based on distribution no ? |
We are waiting for the OCI specification to be released. There is an ongoing discussion about OCI manifest support and a few other parts of the spec might likely get updated too. Until that happens I don't expect any major registry to support any of the new capabilities. |
FYI: RC-3 of |
Thanks for the information |
Ah yes, opened a draft PR to update it (wasn't sure if we wanted pre-releases to be in use, but can move it out of draft if we're okay with that); |
The "OCI Artifact Manifest" has been dropped from the spec and the |
This implements support for OCI Artifact Manifests as described in the OCI 1.1 release candidate specification.
This does not add support for the new subject field in OCI Image Manifests, but it does lay common groundwork to make that a trivial change. This does not implement the referrers list API but does create the links files required to do so. This does not implement any GC. I would like to add those in subsequent pull requests to aid reviewability.
Adresses #3716
This pull request is loosely based on work in https://github.com/oci-playground/distribution by:
Co-authored-by: Sajay Antony sajaya@microsoft.com
Co-authored-by: Tejaswini Duggaraju naduggar@microsoft.com
Co-authored-by: Akash Singhal akashsinghal@microsoft.com
Co-authored-by: Aviral Takkar avtakkar@microsoft.com
Co-authored-by: Julus Liu juliusl@microsoft.com
Co-authored-by: Josh Dolitsky josh@dolit.ski
Co-authored-by: Shiwei Zhang shizh@microsoft.com
Co-authored-by: Brandon Mitchell git@bmitch.net