You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently build Docker images using the linux/arm64/v8 and linux/amd64 platforms, along with QEMU to emulate the arm64 platform. This takes about 50 minutes, most of which is spent building the emulated images.
We currently build Docker images using the
linux/arm64/v8
andlinux/amd64
platforms, along with QEMU to emulate the arm64 platform. This takes about 50 minutes, most of which is spent building the emulated images.GitHub recently announced general availability of their Linux arm64 hosted runners for GitHub Actions: https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/
We can use this to speed up our build time quite a bit by building the arm64 image separately on an arm64 machine. There is an example of building across multiple runners here: https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners. This runs the arm64 and amd64 builds in parallel and then uses a merge job to combine them into a single published tag.
Instead of using a platform matrix, we'd use an os matrix, like this example: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/running-variations-of-jobs-in-a-workflow#example-using-a-multi-dimension-matrix
The text was updated successfully, but these errors were encountered: