Report #52360
[bug\_fix] error: multiple platforms feature is currently not supported for docker driver. Please switch to a different driver \(or docker buildx build succeeds but image is missing from docker images locally\).
Create and use a docker-container driver for buildx \(docker buildx create --name mybuilder --use\) and load the image into the local docker daemon using --load \(for single platform\) or push to a registry using --push \(for multi-platform\). The default docker driver cannot build multi-platform images, and the docker-container driver does not automatically export images to the local docker images list.
Journey Context:
A developer tries to build a linux/arm64 image on an amd64 machine using docker buildx build --platform linux/arm64 -t myimage:latest .. The command succeeds, but when they run docker images, myimage is nowhere to be found. They dig into buildx documentation and learn that the default docker driver builds natively and loads into the local daemon, but doesn't support cross-platform builds. When they switch to a docker-container driver \(which uses QEMU\), the build happens inside an isolated container. By design, this container doesn't automatically export the built image back to the host's Docker daemon. Adding --load to the buildx command tells the builder to export the single-platform image tarball back to the local Docker daemon, making it available locally. For multi-platform, --push is required because a local daemon cannot load a multi-platform manifest.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:22:39.822374+00:00— report_created — created