continuwuation/continuwuity
continuwuation/continuwuity
16
112
Fork 125
Code Issues 136 Pull requests 26 Releases 40 Packages 3 Activity Actions 4

WIP: ci: Compile arm64 natively on the ubuntu-arm64 runner #2155

Draft
morgan wants to merge 1 commit from morgan/arm64-runner into main
pull from: morgan/arm64-runner
merge into: continuwuation:main
Conversation 0 Commits 1 Files changed 3 +210 -10
morgan commented 2026-08-20 08:06:32 +00:00
Owner
Copy link

The arm64 build cross-compiled with the Rust target triple inside an amd64 container and copied the binary out, deliberately avoiding Docker emulation because arm64 emulation is unreliable on some BuildKit instances. A dedicated Ubuntu VM on an M4 Mac Mini is now available under the ubuntu-arm64 label, so each matrix entry carries its own runner label and a native flag, letting individual builds move between runners or build modes without changing the workflow structure.

Where native is set, the new build-native action compiles on the host and assembles the artefact tree, leaving Docker to package the result. The Dockerfile's ARTIFACTS argument selects whether the artefacts come from the builder stage or from out/ in the build context, and everything from prepper onwards is unchanged. Libraries are resolved where the binary was linked, so arm64 images now carry Ubuntu's rather than Debian's.

Also split the architecture flags, since the C and Rust sides need different syntax on ARM. The default aarch64 target only enables neon, so arm64 now passes +crc supported on every 64-bit Raspberry Pi since the Pi 2, and on Neoverse and Apple Silicon. amd64 still passes haswell to both sides, and TARGET_CPU continues to drive the tag suffix.

This only covers arm64 for now. The native path needs persistent storage on the runner, and the amd64 Docker runners don't have that configured. Having several amd64 runners would be fine, the cache would just be less fresh on each, but setting up persistence needs hardware I don't have yet. sccache could point at a shared S3 or MinIO backend if I stood one up, though cargo's target directory has no remote equivalent, so the persistence problem stands either way. I'm happy for this to wait if you'd rather both architectures moved together. Otherwise arm64 can use it now and amd64 follows when the hardware does.

The arm64 build cross-compiled with the Rust target triple inside an amd64 container and copied the binary out, deliberately avoiding Docker emulation because arm64 emulation is unreliable on some BuildKit instances. A dedicated Ubuntu VM on an M4 Mac Mini is now available under the `ubuntu-arm64` label, so each matrix entry carries its own runner label and a native flag, letting individual builds move between runners or build modes without changing the workflow structure. Where native is set, the new build-native action compiles on the host and assembles the artefact tree, leaving Docker to package the result. The Dockerfile's ARTIFACTS argument selects whether the artefacts come from the builder stage or from out/ in the build context, and everything from prepper onwards is unchanged. Libraries are resolved where the binary was linked, so arm64 images now carry Ubuntu's rather than Debian's. Also split the architecture flags, since the C and Rust sides need different syntax on ARM. The default aarch64 target only enables neon, so arm64 now passes `+crc` supported on every 64-bit Raspberry Pi since the Pi 2, and on Neoverse and Apple Silicon. amd64 still passes haswell to both sides, and TARGET_CPU continues to drive the tag suffix. This only covers arm64 for now. The native path needs persistent storage on the runner, and the amd64 Docker runners don't have that configured. Having several amd64 runners would be fine, the cache would just be less fresh on each, but setting up persistence needs hardware I don't have yet. sccache could point at a shared S3 or MinIO backend if I stood one up, though cargo's target directory has no remote equivalent, so the persistence problem stands either way. I'm happy for this to wait if you'd rather both architectures moved together. Otherwise arm64 can use it now and amd64 follows when the hardware does.
ci: Build arm64 images on the native ubuntu-arm64 runner
All checks were successful
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m8s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m14s
Details
Checks / Prek / Check changed files (pull_request) Successful in 8s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
d062fb349e
 
The linux/arm64 legs of build-release and build-maxperf ran on the dind
runner under QEMU emulation. A dedicated Ubuntu VM on an M4 Mac Mini is
now available under the ubuntu-arm64 label, so the arm64 matrix entries
target it directly and build natively.

Each matrix entry carries its own runner label rather than the job pinning
runs-on, keeping the amd64 legs on dind.
ci: Compile arm64 natively on the host runner
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m13s
Details
69afd4d907
 
The arm64 legs of build-release and build-maxperf ran on the dind
runner under QEMU emulation. A dedicated Ubuntu VM on an M4 Mac Mini
is now available under the ubuntu-arm64 label, so each matrix entry
carries its own runner label and the arm64 entries target it. The
amd64 legs stay on dind.

Where the runner architecture matches the target, the new build-native
action compiles on the host and assembles the artefact tree, leaving
Docker to package it. Libraries are resolved on the host because that
is where the binary was linked; resolving them in the container would
ship a different set.

The Dockerfile takes an ARTIFACTS argument selecting whether the
artefacts come from the builder stage or from out/ in the build
context. The prepper and final image stages are unchanged.
morgan force-pushed morgan/arm64-runner from 69afd4d907
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m7s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m13s
Details
to affb609326
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m16s
Details
2026-08-20 12:39:35 +00:00 Compare
morgan changed title from ci: Build arm64 images on the native ubuntu-arm64 runner to ci: Compile arm64 natively on the ubuntu-arm64 runner 2026-08-20 12:40:45 +00:00
morgan changed title from ci: Compile arm64 natively on the ubuntu-arm64 runner to WIP: ci: Compile arm64 natively on the ubuntu-arm64 runner 2026-08-20 12:41:03 +00:00
morgan force-pushed morgan/arm64-runner from affb609326
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m6s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m16s
Details
to b4c89e2421
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m14s
Details
Checks / Prek / Check changed files (pull_request) Successful in 9s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
2026-08-20 13:34:09 +00:00 Compare
morgan force-pushed morgan/arm64-runner from b4c89e2421
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m14s
Details
Checks / Prek / Check changed files (pull_request) Successful in 9s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
to 13afb88ded
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m2s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m18s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
2026-08-20 15:25:25 +00:00 Compare
morgan force-pushed morgan/arm64-runner from 13afb88ded
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m2s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m18s
Details
Checks / Prek / Check changed files (pull_request) Successful in 7s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
to 7e979882bd
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m23s
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m26s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Details
2026-08-20 15:58:36 +00:00 Compare
morgan self-assigned this 2026-08-20 16:53:55 +00:00
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m5s
Details
Checks / Prek / Check changed files (pull_request) Successful in 6s
Required
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m23s
Required
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m26s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Required
Details
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 10s
Required
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin morgan/arm64-runner:morgan/arm64-runner
git switch morgan/arm64-runner
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Abandoned
This pull request appears to be abandoned by its author.

  
Blocked
This pull request or issue is currently blocked from being merged/closed

  
Bug
Something isn't working as intended

  
Changelog
Added
 Changelog entry added

  
Changelog
Missing
 No changelog when one is needed

  
Changelog
None
 Changelog is unnecesary for this change

  
Cherry-picking
Commits picked from other conduit projects

  
Database
This requires or includes changes to the database

  
Dependencies
Something dependency related

  
Dependencies/Renovate
Automatic dependency upgrades by Renovate

  
Difficulty
Easy
 Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
 High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
 Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation
Improvements or additions to documentation

  
Enhancement
New feature or request

  
Good first issue
Good for newcomers

  
Help wanted
Additional eyes and keyboards are required for this one

  
Inherited
Issues that have been inhereted from the project pre-fork

  
Matrix/Administration
Features pertaining to homeserver administration

  
Matrix/Appservices
Features pertaining to the appservice API

  
Matrix/Auth
Features pertaining to authentication

  
Matrix/Client
Features pertaining to client-to-server interactions

  
Matrix/Core
Issues relating to core matrix functionality, such as state resolution and PDU formats

  
Matrix/E2EE
Issues related to end to end encryption

  
Matrix/Federation
Features pertaining to server-to-server interactions

  
Matrix/Hydra
Issues related to room version 12 and related changes (temporary label)

  
Matrix/MSC
Features pertaining to unstable matrix features

  
Matrix/Media
Features pertaining to media interactions

  
Matrix/T&S
Changes or issues related to trust & safety tooling

  
Merge
This PR is ready to be merged

  
Merge/Manual
This PR should be manually merged

  
Merge/Squash
This PR should be squashed when it is merged

  
Meta
Related to housekeeping, maintenance, or other repo-meta.

  
Meta/CI
Issues related to CI changes

  
Meta/Packaging
Packaging

  
Priority
Blocking
 This issue is blocking the next release

  
Priority
High
 This issue is very important

  
Priority
Low
 This issue is of a rather low priority

  
Security
This item is related to general security

  
Status
Confirmed
 This issue has enough information and is confirmed

  
Status
Duplicate
 This issue or pull request already exists

  
Status
Invalid
 This issue doesn't seem right

  
Status
Needs Investigation
 This issue needs further investigation

  
Support
Questions or support requests

  
bob the builder
pdu logic rewrite starring nexus nicholson

No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
morgan
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!2155
No description provided.