Files
muse/.github/workflows
T
Aryan SinghandClaude Opus 5 0dca779f59 Publish arm64 alongside amd64
muse is now the front door of a public project, and it was the only
image in that stack without an arm64 build. Raspberry Pis, arm64 NASes
and Ampere VPSes are a large share of self-hosters, so amd64-only made
the whole stack un-runnable for them — gluetun, slskd, soularr, lidarr,
navidrome and the socket proxy all already publish both.

Three parts, because changing `platforms:` alone would have failed:

- setup-qemu-action registers the binfmt handlers buildx needs to
  produce arm64 on an amd64 runner. Without it the build errors with
  "exec format error"; it does not quietly fall back to amd64.
- The web stage is pinned to --platform=$BUILDPLATFORM so the Next.js
  build runs natively once instead of being emulated per platform. It
  is the expensive step, and its output is static HTML/JS/CSS with no
  native code, so the bytes are identical either way. This is what
  makes the old comment's "3-5x slower for nothing" no longer true.
- platforms: linux/amd64,linux/arm64.

Verified locally before pushing: both platforms build in ~52s, and the
loaded arm64 image reports aarch64 with uvloop, watchfiles, httptools
and pydantic_core all importing, `import app` succeeding, and the
static UI present.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0dca779f59 · 2026-08-06 00:51:31 -05:00
History
..
2026-08-06 00:51:31 -05:00