You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The webhook accepts arm64, and the launcher launches a Graviton runner for it: m7g, m6g and m8g at the job's size, from a second launch template. That template is the arm64 counterpart of today's: the AL2023 arm64 image through resolve:ssm:, the same disk, IMDSv2 and tags, and no instance profile. make hand-launch takes an architecture.
Acceptance criteria
Webhook tests: arm64 is accepted; x64 together with arm64 is outside the contract.
Launcher tests: arm64 jobs use the arm64 launch template and the Graviton families at each size.
The launcher's role allows launching from both launch templates and nothing more.
Proven live: one ci-spot / arm64 job runs and uname -m prints aarch64.
README, docs/stack.md and the runbook describe arm64.
Owner decision (2026-11-14, in the build session): x64 runners also launch on m8i and m8a, offered at .large–.4xlarge in all three of the stack's AZs (commit 68648e3).
Activity
Merge ticket #24: arm64 on EC2, live proof pending
sodre commentedon Nov 14, 2026
Live:
[self-hosted, ci-spot, ci-cpu-4, arm64]ran on i-01c0d1d796da39d12, an m8g.xlarge,uname -m= aarch64: https://github.com/zeroae/ci-runner-canary/actions/runs/43541777893sodre commentedon Nov 14, 2026
Owner decision (2026-11-14, in the build session): x64 runners also launch on
m8iandm8a, offered at .large–.4xlarge in all three of the stack's AZs (commit 68648e3).