fix(ci): multi-arch build #3884
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kolesnikovae
force-pushed
the
fix/multi-arch-build
branch
from
425ca3b to
72f5a1e
Compare
korniltsev
approved these changes
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting from
buildxv0.10.0,docker manifestcan no longer be used to create multi-platform images. This is due to a change in the output format, which now includes a provenance attestation and creates a manifest list – something thatdocker manifestdoes not expect and cannot handle. Instead,docker buildx imagetoolsshould be used to craft multi-architecture manifests.We should also consider using
docker buildx imagetoolsin weekly builds, where we re-push images using the standard Docker, which does not add attestation and, therefore, avoids this issue.