-
Notifications
You must be signed in to change notification settings - Fork 181
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
oras tag
should not create referrers tags
#1436
Closed
qweeah opened this issue
Jun 28, 2024
· 4 comments
· Fixed by #1435 or #1577 · May be fixed by benhoff/build#3, HeyMeco/build#1 or functionland/armbian-build#1
Closed
oras tag
should not create referrers tags
#1436
qweeah opened this issue
Jun 28, 2024
· 4 comments
· Fixed by #1435 or #1577 · May be fixed by benhoff/build#3, HeyMeco/build#1 or functionland/armbian-build#1
Labels
bug
Something isn't working
Comments
BTW this bug generates unwanted referrer tags (256-xxx) ONLY in registries that haven't implemented OCI Distribution Spec v1.1.0. |
4 tasks
Closing as it's resolved. |
This was referenced Dec 5, 2024
This was referenced Dec 16, 2024
Open
Closed
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
This was referenced Dec 16, 2024
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although tagging a referrer artifact manifest is discouraged, it is still doable. However, re-tagging is implemented as pushing the exact manifest again to the remote server. According to the distribution-spec, if the remote server does not support referrers API, it will go for the referrers tag schema case. However, it is not necessary since the manifest is already there, we are just adding a new tag not really pushing a new manifest.
In summary, tagging a referrers manifest should never go for the tag schema even if the server does not support referrers API since the referrer manifest is already there on the server.
Originally posted by @shizhMSFT in #1435 (comment)
The text was updated successfully, but these errors were encountered: