-
Notifications
You must be signed in to change notification settings - Fork 542
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
FR: Support OCI reference types #1434
Comments
To put this in crane we'll need to rely on the new APIs and conventions proposed by the OCI reference types working group:
We expect these spec changes to be merged in soon 🤞, then for these changes to start trickling out to registry implementations over the next few years. The fallback behavior described in those changes relies on tag naming conventions, for compatibility with registries that haven't adopted the new specs yet. @jdolitsky has been hacking on changes to go-containerregistry and crane to add support for these APIs here: main...oci-playground:main When these APIs and conventions are adopted and the changes above are merged into ggcr, the idea is you'll be able to |
It looks like these PRs are merged, so shall we start working on this issue? |
See #1455 |
This issue is stale because it has been open for 90 days with no |
Once I run
crane copy,
it'll (at the time of writing this) copy only the image itself, but the image may have other materials attached to it such as SBOMs, attestations, signatures, etc.cosign copy
command supports that, but in crane, we do not have support for this, so, it'd be better copying these materials (if any) with the image itself optionally.cc: @Dentrax @imjasonh
The text was updated successfully, but these errors were encountered: