Repository navigation
Split Docker builds across native amd64 and arm64 runners - #75
Merged
Merged
Conversation
Owner
|
This needs to be rebased on the latest master to fix conflicts from merging the other workflow PRs. |
vlnst
force-pushed
the
docker-native-arm
branch
from
October 18, 2026 17:13
d9e838c to
b6996e8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Docker Build workflow takes 30 to 50 minutes per run because the arm64 image is compiled under QEMU emulation on an x86 runner.
This builds each platform on its own native runner in parallel, using the ubuntu-24.04-arm runners that are free for public repos, and then merges the two digests into one multi-arch tag, following the pattern from Docker's multi-platform docs. Each platform gets its own gha cache scope so they don't overwrite each other. On my fork the whole workflow ran in about 5 minutes with a cold cache. The merge job only runs on master and tags, so it couldn't be exercised there. This is based on #74 and includes its commit until that is merged.