buildx "docker exporter does not support exporting manifest lists" (--load multi-platform) in CI

By Kaveh Alemi·Latchkey

A multi-platform build produces a manifest list, but the local docker image store can only hold a single-platform image. So --load of a --platform linux/amd64,linux/arm64 build is rejected; such builds must be pushed instead.

What this error means

A multi-platform build with --load fails with "ERROR: docker exporter does not currently support exporting manifest lists" or "failed to solve: docker exporter does not support exporting multiple platforms".

ERROR: failed to solve: docker exporter does not currently support exporting manifest lists

Common causes

Loading a multi-platform image locally

--load targets the docker image store, which has no concept of a manifest list, so a multi-arch result cannot be loaded.

Mixing --platform with --load by habit

A workflow that worked for a single platform fails once a second platform is added while still using --load.

How to fix it

Push multi-platform images instead of loading

1. Replace --load with --push for multi-platform builds.
2. Provide a registry tag so the manifest list has a home.
3. If you need a local image, build a single platform with --load.

docker buildx build --platform linux/amd64,linux/arm64 \
  --push -t ghcr.io/acme/app:ci .

Build one platform locally when you must load

For a local smoke test, drop the extra platform so the result is a single image the store accepts.

docker buildx build --platform linux/amd64 --load -t app:ci .

How to prevent it

• Use --push for any build with more than one platform.
• Reserve --load for single-platform local images.
• Enable the containerd image store if you need local multi-arch images.

Frequently asked questions

Related guides

References

• Docker documentation
• Docker build cache
• GitHub Actions documentation