Docker · tool · fg-0261

FROM a locally built image tries to pull from docker.io when the buildx builder uses the docker-container driver

load metadata for docker.io/library/my_base_image:latest fails although docker images lists my_base_image

Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100

Cause

A docker-container builder runs BuildKit inside its own container with its own content store, so it cannot read images from the engine's image store and resolves the name against a registry instead.

Fix

Build images that depend on local images with the default docker builder, push the base image to a registry first, or switch to the containerd image store. Check which builder is active with docker buildx ls.

Apply

docker buildx use default
docker buildx build -t my_base_image .
docker buildx build -f final.dockerfile --build-arg BASE_IMAGE=my_base_image .

Affects: Docker Buildx with docker-container, kubernetes, or remote drivers (common after docker buildx create --use or in CI with setup-buildx-action), as of October 2026

Sources

• https://github.com/docker/buildx/issues/1453
• https://docs.docker.com/build/building/multi-platform/

claude mcp add --transport http footgun https://getfootgun.com/api/mcp