Skip to content
Latchkey

Docker "docker exporter does not currently support exporting manifest lists" (--load Multi-Platform)

You asked buildx to --load a multi-platform build into the local Docker image store, but that store holds only single-platform images. A manifest list (multi-arch) cannot be loaded - it has to be pushed to a registry instead.

What this error means

A docker buildx build --platform linux/amd64,linux/arm64 --load . fails with docker exporter does not currently support exporting manifest lists. A single-platform --load, or the same build with --push, works fine.

docker buildx output
ERROR: docker exporter does not currently support exporting manifest lists
# from: docker buildx build --platform linux/amd64,linux/arm64 --load .

Common causes

The local image store is single-platform only

The classic Docker image store keeps one platform per tag. A multi-platform result is a manifest list, which --load cannot represent there.

--load used where --push was intended

Multi-arch images are meant to live in a registry. Using --load (local) instead of --push (registry) for a multi-platform build is the mismatch.

How to fix it

Push multi-platform builds to a registry

Use --push so the manifest list lands in a registry that can hold it.

Terminal
docker buildx build --platform linux/amd64,linux/arm64 \
  --push -t myorg/api:1.4.2 .

Load one platform if you need it locally

When you must --load, build only the platform you intend to run.

Terminal
docker buildx build --platform linux/amd64 --load -t myorg/api:1.4.2 .

How to prevent it

  • Pair multi-platform builds with --push, single-platform with --load.
  • Build only the needed platform when a local image is required.
  • Consider the containerd image store if you need multi-arch images locally.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →