From bee4e5ef4004cfecf3eca42294bec4046e6a8c21 Mon Sep 17 00:00:00 2001 From: Douglas Francis Date: Sat, 12 Sep 2026 14:21:58 +0100 Subject: [PATCH] fix(deploy): build images for linux/arm64, not amd64 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .github/workflows/deploy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 79315e0..97bab2a 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -52,7 +52,7 @@ jobs: push: true # Must match your EC2 instance architecture. # t3.* = linux/amd64. t4g.* (Graviton) = linux/arm64. - platforms: linux/amd64 + platforms: linux/arm64 tags: | ${{ steps.ecr.outputs.registry }}/${{ env.ECR_REPOSITORY }}:${{ steps.meta.outputs.tag }} cache-from: type=gha