Leverage multi-CPU architecture support
Estimated reading time: 5 minutes
Docker images can support multiple architectures, which means that a single image may contain variants for different architectures, and sometimes for different operating systems, such as Windows.
When running an image with multi-architecture support,
selects the image variant that matches your OS and architecture.
Most of the Docker Official Images on Docker Hub provide a variety of architectures.
For example, the
busybox image supports
s390x. When running this image
amd64 machine, the
x86_64 variant is pulled and run.
Multi-arch support on Docker Desktop
Docker Desktop provides
binfmt_misc multi-architecture support,
which means you can run containers for different Linux architectures
ppc64le, and even
This does not require any special configuration in the container itself as it uses
from the Docker for Mac VM. Because of this, you can run an ARM container,
ppc64le variants of the busybox image.
Build multi-arch images with Buildx
Docker is now making it easier than ever to develop containers on, and for Arm servers and devices. Using the standard Docker tooling and processes, you can start to build, push, pull, and run images seamlessly on different compute architectures. In most cases, you don’t have to make any changes to Dockerfiles or source code to start building for Arm.
Docker introduces a new CLI command called
buildx. You can use the
command on Docker Desktop for Mac and Windows to build multi-arch images, link
them together with a manifest file, and push them all to a registry using a
single command. With the included emulation, you can transparently build more
than just native images. Buildx accomplishes this by adding new builder
instances based on BuildKit, and leveraging Docker Desktop’s technology stack
to run non-native binaries.
Build and run multi-architecture images
docker buildx ls command to list the existing builders. This displays
the default builder, which is our old builder.
$ docker buildx ls NAME/NODE DRIVER/ENDPOINT STATUS PLATFORMS default * docker default default running linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v6
Create a new builder which gives access to the new multi-architecture features.
$ docker buildx create --name mybuilder mybuilder
docker buildx create --name mybuilder --use to create a new
builder and switch to it using a single command.
Switch to the new builder and inspect it.
$ docker buildx use mybuilder $ docker buildx inspect --bootstrap [+] Building 2.5s (1/1) FINISHED => [internal] booting buildkit 2.5s => => pulling image moby/buildkit:master 1.3s => => creating container buildx_buildkit_mybuilder0 1.2s Name: mybuilder Driver: docker-container Nodes: Name: mybuilder0 Endpoint: unix:///var/run/docker.sock Status: running Platforms: linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v6
Test the workflow to ensure you can build, push, and run multi-architecture images. Create a simple example Dockerfile, build a couple of image variants, and push them to Docker Hub.
The following example uses a single
Dockerfile to build an Ubuntu image with cURL
installed for multiple architectures.
Dockerfile with the following:
FROM ubuntu:20.04 RUN apt-get update && apt-get install -y curl
Build the Dockerfile with buildx, passing the list of architectures to build for:
$ docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t username/demo:latest --push . [+] Building 6.9s (19/19) FINISHED ... => => pushing layers 2.7s => => pushing manifest for docker.io/username/demo:latest 2.2
username is a valid Docker username.
--platformflag informs buildx to generate Linux images for AMD 64-bit, Arm 64-bit, and Armv7 architectures.
--pushflag generates a multi-arch manifest and pushes all the images to Docker Hub.
Inspect the image using
docker buildx imagetools.
$ docker buildx imagetools inspect username/demo:latest Name: docker.io/username/demo:latest MediaType: application/vnd.docker.distribution.manifest.list.v2+json Digest: sha256:2a2769e4a50db6ac4fa39cf7fb300fa26680aba6ae30f241bb3b6225858eab76 Manifests: Name: docker.io/username/demo:latest@sha256:8f77afbf7c1268aab1ee7f6ce169bb0d96b86f585587d259583a10d5cd56edca MediaType: application/vnd.docker.distribution.manifest.v2+json Platform: linux/amd64 Name: docker.io/username/demo:latest@sha256:2b77acdfea5dc5baa489ffab2a0b4a387666d1d526490e31845eb64e3e73ed20 MediaType: application/vnd.docker.distribution.manifest.v2+json Platform: linux/arm64 Name: docker.io/username/demo:latest@sha256:723c22f366ae44e419d12706453a544ae92711ae52f510e226f6467d8228d191 MediaType: application/vnd.docker.distribution.manifest.v2+json Platform: linux/arm/v7
The image is now available on Docker Hub with the tag
can use this image to run a container on Intel laptops, Amazon EC2 A1 instances,
Raspberry Pis, and on other architectures. Docker pulls the correct image for the
current architecture, so Raspberry Pis run the 32-bit Arm version and EC2 A1
instances run 64-bit Arm. The SHA tags identify a fully qualified image variant.
You can also run images targeted for a different architecture on Docker Desktop.
You can run the images using the SHA tag, and verify the architecture. For example, when you run the following on a macOS:
$ docker run --rm docker.io/username/demo:latest@sha256:2b77acdfea5dc5baa489ffab2a0b4a387666d1d526490e31845eb64e3e73ed20 uname -m aarch64
$ docker run --rm docker.io/username/demo:latest@sha256:723c22f366ae44e419d12706453a544ae92711ae52f510e226f6467d8228d191 uname -m armv7l
In the above example,
uname -m returns
armv7l as expected,
even when running the commands on a native macOS or Windows developer machine.