Docker / Images, Dockerfiles & Build Reliability
Find the builder that actually owns a Docker build's output
A remote or containerized BuildKit builder can produce artifacts outside the local Engine store. Inspect the selected builder first.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker buildx lsRead the result
The list shows builder instances, drivers and supported platform context. Availability does not guarantee current registry access or sufficient remote capacity.
Resolve and verify
Compare the pipeline's builder and output mode with the intended image destination. Correct the explicit builder or export settings through the release configuration.
Before changing production
Do not create another builder or delete existing instances just because the result is absent from docker image ls.