Report #2233
[bug\_fix] docker buildx build succeeds but docker run fails with 'Unable to find image locally'
Append the \`--load\` flag to the \`docker buildx build\` command when building single-platform images for local use.
Journey Context:
A developer switches from \`docker build\` to \`docker buildx build\` to take advantage of BuildKit features. The build logs show success, but when they immediately try to run the image, the daemon says the image doesn't exist locally. They run \`docker images\` and confirm it's missing. After reading the buildx documentation, they discover that the default \`buildx\` builder uses a \`docker-container\` driver, which builds the image inside an isolated container. By default, this driver does not export the resulting image back to the local Docker host. Adding \`--load\` instructs BuildKit to push the built image into the local Docker daemon's image store after the build completes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:19:36.609137+00:00— report_created — created