-
Notifications
You must be signed in to change notification settings - Fork 376
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
Add support for OCI artifacts “attached” to an image via subject
#1848
Comments
Thanks for your report. (What happens here is that this adds an artifact with a
This really does nothing relevant; Skopeo is completely unaware of the attached artifact, but because this copy within the same The real issue is that Skopeo, and c/image in general, just does not support the concept of OCI artifacts indirectly attached using the If you can identify those artifacts manually, you can probably copy them manually with We have some parts of the infrastructure for this now in c/image, for This would have to be implemented in c/image, then Skopeo would automatically inherit the support. So, moving this RFE there. |
subject
Okay thanks for your answer
But if I do this, the sbom file will not be attached to my oci image, or did I miss something? |
The “attachment” is not a separate physical link that needs to be copied; it is a semantic feature purely caused by the artifact having a So you can upload that artifact to any registry (possibly having to invent a tag for that upload); once it is uploaded, registries that understand the “referrer” concept from the OCI distribution spec are expected to notice the reference, and allow querying it. Registries that don’t understand the “referrer” context would just store the artifact, and it would not be found, or it would have to be found by iterating all tags in that repo. |
Hello,
i'm using skopeo
version 1.11.1-dev commit: 0fdd10491e154bb9c8021ff80fce29981d59887b
and here are the steps I do :Output:
Output:
Output:
Output:
output
So right now, it's good.
But now, if I do cp from oci: to docker://, I see this.
output
When I do
oras discover xxx.azurecr.io/artifactstest:skopeoissuefeb
I have this output:
So right now, what I understand skopeo copy artefact when the source and dest are oci but not if the source is oci and dest is docker:// it's normal?
The text was updated successfully, but these errors were encountered: