What an ARM job gets on our runners, in one place. Each answer links to the page with the detail.
runnersio-<n>vcpu-ubuntu-2404-arm, -ubuntu-2204-arm and -ubuntu-2604-arm are Ubuntu 24.04, 22.04 and 26.04 on 64-bit ARM (aarch64), in 2, 4, 8 and 16 vCPU. They take the place of GitHub's ubuntu-24.04-arm, ubuntu-22.04-arm and ubuntu-26.04-arm.
Runner labels has the memory and disk of each size, and which of GitHub's labels each replaces.
The same image as on x64, built for ARM64: the same tools, as the ARM64 build of each, with passwordless
sudo, Docker and the tool cache. The runner image lists the versions.actions/cache, served by our cache with no change to the workflow; see the Actions cache.A terminal into the running job, once an owner or admin has switched it on; see Debugging a running job.
Each job gets its own virtual machine, started fresh from our image and shared with no other job, and destroyed when the job ends.
A tool or a container image that is built for x64 only. It will not run: a container needs an
arm64build of its image.A browser. Chromium is published for x64 only, so the ARM64 image has none.
Sticky disks. An ARM job runs with an empty disk that is thrown away when it ends; see which labels get one.
/dev/kvm, so no nested virtualisation.Windows on ARM and macOS. Keep those jobs on GitHub's runners; a workflow can mix ours and GitHub's job by job.
A minute on a 2 vCPU ARM runner counts as the same run-minutes as a minute on the 2 vCPU Ubuntu x64 runner. A minute on a larger ARM runner counts as fewer run-minutes than a minute on the Ubuntu x64 runner of the same size. Runner labels has the figure, and the pricing page has the rate.