Repository navigation
fix: build release images with matching target architecture - #3325
Merged
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Signed-off-by: Jeff Rescignano <jeffr@defenseunicorns.com>
JeffResc
force-pushed
the
fix/release-image-arch
branch
from
August 3, 2026 15:56
57a6367 to
a7aacf0
Compare
jiparis
approved these changes
Aug 3, 2026
jiparis
left a comment
jiparis
left a comment
Member
There was a problem hiding this comment.
Good catch, thanks for the fix.
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
3 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.
Summary
Fix the release image build for arm64.
The release config now builds the service binaries and copied plugins for
linux_arm64. It also setsgoarchon each Docker image entry. This makes GoReleaser use the correct binary set for each image architecture.Closes #3324
Root Cause
The arm64 Docker images used
--platform=linux/arm64, but the Docker build context still received amd64 binaries. The service binaries and copied plugins were only built forlinux_amd64. The Docker entries also did not select an architecture-specific artifact set.Changes
control-planeforlinux_arm64.artifact-casforlinux_arm64.linux_arm64.goarch: amd64orgoarch: arm64on Docker image entries.Verification
Ran:
Verified that the rebuilt local arm64 images are labeled
linux/arm64.Extracted these binaries from the rebuilt arm64 images and verified each one is
ARM aarch64:/control-plane/artifact-cas/plugins/chainloop-plugin-dependency-track/plugins/chainloop-plugin-discord-webhook/plugins/chainloop-plugin-smtp