Apple Silicon Docker pain
- Docker images built only for x86_64, also called amd64, don’t run natively on Apple Silicon Macs; Docker can emulate them, but Docker’s own docs say that path is slower. - Docker documents three ways to ship multi-platform images: emulation with QEMU, multiple native build nodes, or cross-compilation with BuildKit, so teams can publish both amd64 and arm64 from one tag. - Apple Silicon support is now standard in Docker Desktop, which makes architecture mismatches a day-to-day developer workflow issue rather than a niche setup problem. (docs.docker.com)
A Docker image is a packaged app plus its runtime, and it has to match the processor inside the machine that runs it. Apple Silicon Macs use Arm chips, while many older container images still target Intel’s x86_64, also called amd64. (docs.docker.com 1) (docs.docker.com 2) When an amd64 image lands on an Apple Silicon Mac, Docker can still run it through emulation instead of native execution. Docker’s documentation says emulation is the easiest way to start, but it is much slower than native builds and runs for compute-heavy tasks. (docs.docker.com) That slowdown is the root of the “Docker pain” many MacBook developers describe. The issue is not that containers are broken on Apple hardware; it is that a single-architecture image forces an Arm laptop to pretend it is an Intel machine. (docs.docker.com 1) (docs.docker.com 2) Docker’s fix is multi-platform publishing. In plain terms, one image tag can point to separate amd64 and arm64 variants, and the container runtime pulls the version that matches the host processor. (docs.docker.com) (docker.com) Docker documents three main ways to produce those images: QEMU emulation, multiple native build nodes, and cross-compilation with BuildKit. It says multiple native nodes give better support and performance than relying on emulation alone. (docs.docker.com) That pushes the problem upstream, into how teams build and publish software. If a company’s continuous integration pipeline only emits amd64 images, every Apple Silicon developer inherits the emulation penalty on their laptop. (docs.docker.com) Docker has also spent the past few years making Apple Silicon a first-class desktop target. Its Mac install documentation lists separate binaries for Apple Silicon, and says Rosetta 2 is no longer strictly required for Docker Desktop in most cases, though a few optional command-line features may still need it. (docs.docker.com) On newer Macs, Docker also offers its own virtual machine manager, called Docker VMM, for Apple Silicon on macOS 12.5 and later. That changes the virtualization layer, but it does not remove the need for an arm64 image if the container itself was built only for amd64. (docs.docker.com 1) (docs.docker.com 2) The practical lesson is simple: if teams want Intel servers and Apple laptops to share the same workflow, they have to ship both architectures. Otherwise, the container may still run on a MacBook, but it runs through translation instead of at native speed. (docs.docker.com)
