Are arm64 runners currently unavailable?

My arm64 job has been queued since yesterday (3 November), while amd64 finished fine. The runner list now only shows amd64 runners, but the docs still list ci-arm1.

Is it down temporarily, or has something changed?

Yes, they were offline for some days while we restructured the runners. It took us a bit longer for the FJ runners than the Crow ones due to some security checks.

arm64 runners are back (and now 3x as fast as before as M4/M5 macMini’s are now in use). Doc updates will follow!

1 Like

That’s great to hear, cheers​:clinking_beer_mugs:!

Jobs are being picked up now, but Docker builds still fail on both ARM64 runners. Neither node:24-bookworm nor the default DinD image has a working Docker socket. docker:2375 doesn’t resolve, and starting dockerd manually fails with an iptables permission error.

Is there a particular Docker setup we should use on the new runners?

Sorry for the disruption. Docker builds work again on the arm64 runners.

One change for your job: the daemon comes with the default image of the docker label, so a custom container: image such as node:24-bookworm won’t have one. Remove the container: block and any step that installs Docker or starts dockerd, and docker build works with no setup.
We had to make some changes behind the scenes as running securely on the macOS hosts is different from the previous Linux host.

Details are in the (updated) docs: Forgejo Actions | CodeFloe

Let us know how it goes!

1 Like

All sorted now, thanks! The new runners are much faster than the old ones.