Published Docker image lacks ARM64 support (“no matching manifest for linux/arm64/v8”)

[FK78]

When trying to run the prebuilt image ghcr.io/quackbackio/quackback:latest on an ARM64 machine (Apple Silicon, AWS Graviton, etc.) via Docker Compose, the pull fails with:

no matching manifest for linux/arm64/v8 in the manifest list entries

This means the published image is currently only built for linux/amd64. ARM64 users cannot pull or run it without emulation (which is slow and often not desired).

Steps to reproduce

1. On an Apple Silicon Mac (or any aarch64 host), run the provided docker compose up -d with the ghcr.io/quackbackio/quackback:latest image.
2. Docker attempts to pull the image and immediately fails with the above error.

Expected behavior

The image should be available natively for linux/arm64 (or as a multi‑arch manifest list) so that Docker automatically pulls the correct architecture.

Suggested solution

Publish a multi‑architecture image that includes both linux/amd64 and linux/arm64. This can be done with Docker Buildx:

docker buildx build \
  --platform linux/amd64,linux/arm64 \
  -t ghcr.io/quackbackio/quackback:latest \
  -f apps/web/Dockerfile \
  --push .

Alternatively, if the CI already uses a GitHub Actions workflow, adding a docker/setup-buildx-action step and using platforms: linux/amd64,linux/arm64 in the build‑push action will do the job.

Additional context

• The oven/bun base image fully supports ARM64, so only the build/push step needs to be updated.
• Many similar projects already ship multi‑arch images (Grafana, Metabase, etc.) – this is becoming standard practice.
• Without this change, ARM64 users must either emulate (poor performance) or build the image themselves, which defeats the purpose of providing a ready‑to‑use container.