Skip to content

Use the native arm64 headless build for Factorio 2.1+ - #620

Merged
fank merged 2 commits into
factoriotools:masterfrom
Szer:native-arm64
Nov 2, 2026
Merged

fank merged 2 commits into
factoriotools:masterfrom
Szer:native-arm64

Conversation

@Szer

@Szer Szer commented Sep 19, 2026

Copy link
Copy Markdown

Factorio 2.1 now ships a native ARM64 Linux headless build (FFF-446). The arm64
image still downloads the x64 build and runs it under box64.

With this change the arm64 image downloads the linux-arm64 archive when the
version has one and skips box64. Versions without one (2.0.x stable) build
exactly as before.

  • New build arg SHA256_ARM64, set from a new optional sha256_arm64 field in
    buildinfo.json. build.py passes it, update.sh fills it from the sha256sums
    page when the arm64 archive exists.
  • The native archive has bin/arm64, so the image adds a bin/x64 symlink and
    all scripts keep working unchanged.
  • Same for the rootless Dockerfile. README note updated.

Tested: arm64 and amd64 builds of 2.1.19, and the arm64 image running a
modded Space Age save on an Azure Cobalt 100 node with players connected.

Factorio 2.1 ships a native ARM64 Linux headless build. When a version has
one (sha256_arm64 in buildinfo.json, passed as build arg SHA256_ARM64), the
arm64 image downloads it instead of the x64 build and skips box64. Versions
without it build exactly as before. The native archive has bin/arm64, so
the image adds a bin/x64 symlink to keep the scripts unchanged.
@EugeneKay

EugeneKay commented Sep 24, 2026 •

Copy link
Copy Markdown

I have built this on a Raspberry Pi 5. I verified the 2.1, 2.1.20, latest, 2.1-rootless, 2.1.20-rootless, and latest-rootless images build, run, and can be connected-to by a Multiplayer Client locally on the LAN. Works good!

@tisba

tisba commented Oct 20, 2026

Copy link
Copy Markdown

Awesome, this is great!

I don't know much about how images are build, but do you think a multi-arch image would be possible too?

@fank

fank commented Nov 2, 2026

Copy link
Copy Markdown
Member

Thank you @Szer for contributing native ARM64 support and testing on real hardware! Thanks also to @EugeneKay for the Raspberry Pi validation.

I refreshed this branch against current master without rewriting your commit, and pushed 1e11e2c. This fixes all four jq expressions, resolves buildinfo to 2.1.24 with its published ARM64 checksum, enables native ARM64 for Compose builds, fixes the string-keyed tag array exposed by testing, and adds regression tests plus CI.

GitHub regression tests, ShellCheck and Hadolint all pass. All six final-head build/version checks pass: 2.1.24 regular/rootless on AMD64 and ARM64, plus legacy 2.0.77 regular/rootless on ARM64 with box64. All four 2.1.24 images passed save-generation, server-startup and save-on-shutdown smoke tests. ARM64 was tested via QEMU, not physical ARM hardware; no multiplayer client join was tested.

Legacy caveat: a 2.0.77 rootless shutdown test reported SIGSEGV after saving and Goodbye under nested box64/QEMU. I am comparing unchanged master; that extra shutdown check is not a pass.

Leaving this open and unmerged for the maintainer decision.

Composed by the coding-assistant agent, posted under my account.

@fank

fank commented Nov 2, 2026

Copy link
Copy Markdown
Member

Follow-up: the legacy 2.0.77 rootless shutdown SIGSEGV reproduces on an image built from unchanged master f1bdaaf, with the same nested box64/QEMU setup. Both baseline and PR images save to 100%, close the socket, print Goodbye, then report SIGSEGV and exit 1. This is an existing legacy-runtime failure in this test environment, not introduced by this PR; it remains unresolved and is not counted as a passing shutdown test.

The native 2.1.24 four-image smoke matrix passes, all six build/version probes pass, and all three GitHub checks pass on 1e11e2c. The PR is mergeable and left unmerged.

Composed by the coding-assistant agent, posted under my account.

@fank
fank merged commit c893445 into factoriotools:master Nov 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants