-
Notifications
You must be signed in to change notification settings - Fork 509
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
index annotations not supported for single platform export #2591
Comments
Can you post an example build and what export options do you use. Was your (single-platform) build result image index before? |
This error is returned by buildkit here. #2546 should only have affected the inputs to |
This is the command line ran by the GitHub action :
Not sure if that's what you're asking, but running
|
Thank you for providing that. This looks like my hunch is right. You're using the
In the short term, the easiest fix would be for you to remove all but the For whether this should produce an index I need to defer to @tonistiigi |
Looks correct that there is no index for that build. Normally, we now have index now for adding attestations but in this build default provenance is explicitly disabled. Another way to opt-in to index in this case should be |
Thanks! |
OK to close this once docker/docs#20419 is merged in? @dvdksn @meriouma |
Also remove the index annotation level -- for single platform export all we need it the manifest. See: docker/buildx#2591
Contributing guidelines
I've found a bug and checked that ...
Description
We just updated to buildx 0.16 and we are now getting the error
index annotations not supported for single platform export
when using the GitHub actiondocker/build-push-action
with a single platform.Expected behaviour
Annotations on a single platform works as before. The OCI Image Index specification specifies that annotations are supported on the image index, and :
Actual behaviour
The build fails with
Buildx version
github.com/docker/buildx v0.16.0 10c9ff9
Docker info
No response
Builders list
The text was updated successfully, but these errors were encountered: