fix(deploy): build images for linux/arm64, not amd64 - #407
Merged
Conversation
The target EC2 instance is a t4g.small, which is AWS Graviton — arm64. An amd64 image pushes to ECR without complaint and then fails at container start with "exec format error", which reads like a corrupt image rather than an architecture mismatch. The adjacent comment already documented the mapping (t3.* = amd64, t4g.* = arm64) and stays accurate, so it is left as is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
One-line change to
.github/workflows/deploy.yml.# Must match your EC2 instance architecture. # t3.* = linux/amd64. t4g.* (Graviton) = linux/arm64. - platforms: linux/amd64 + platforms: linux/arm64The target instance is a t4g.small — AWS Graviton, so arm64, not x86.
This is worth fixing before the first deploy rather than after, because the failure mode is misleading: an amd64 image pushes to ECR without complaint, and only fails at container start with
exec format error. That reads like a corrupt or broken image, not an architecture mismatch, so it tends to send you looking in the wrong place.The adjacent comment already documented the mapping and remains accurate, so it is untouched.
Verification
git diff --numstat→1 1 .github/workflows/deploy.yml. Nothing else changed;ci.ymluntouched.A repo-wide grep confirms
linux/amd64now appears nowhere in this repo except that explanatory comment, andplatforms:appears exactly once.Note the frontend needs the same change — escrow-frontend has a matching PR. Both must land before the first deploy, or the two images end up on different architectures.
🤖 Generated with Claude Code