feat(ci): build container for linux/amd64 and linux/arm64#52
Merged
Conversation
Adds QEMU setup and multi-platform build to the GHCR workflow so users on Apple Silicon, AWS Graviton, and Raspberry Pi pull native arm64 images instead of running amd64 under emulation. Build time roughly doubles but the published manifest now resolves correctly on both architectures.
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
1 participant
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.
Follow-up to #51. The published image was amd64-only, so anyone on Apple Silicon, AWS Graviton, or Raspberry Pi had to pull under emulation (verified locally —
docker pull ghcr.io/teslakoile/huly-cli:lateston arm64 reportsno matching manifest for linux/arm64/v8without--platform linux/amd64).What changed
docker/setup-qemu-action@v4.0.0step before Buildx so the runner can cross-build for non-native platforms.platforms: linux/amd64,linux/arm64on the build-push step. Buildx produces a multi-arch manifest list; clients pull the matching arch automatically.Notes
masterand tags.type=gha,mode=max) is per-platform, so subsequent builds still benefit from layer reuse.