fix: resolve architecture mismatch for multi-arch docker builds#688
Merged
Conversation
Member
|
Temporarily closing and reopening to trigger PR CI for the latest maintainer-pushed commit, because this workflow only runs pull_request CI on opened/reopened. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The build failed on arm64 systems with an exec format error because using $BUILDPLATFORM forced the final stages to pull x86-based images instead of those matching the target architecture.To fix this, the Dockerfile now uses $TARGETPLATFORM for the final stages to ensure the correct native JRE and Distroless base images are pulled for each architecture. Additionally, the CI workflow now includes QEMU to enable proper emulation and multi-arch support for both amd64 and arm64 during the build process.
should resolve #681