Depot: Docker API version mismatch breaks --load, override or push/pull

Depot: Docker API version mismatch breaks --load, override or push/pull

TL;DR

If depot build succeeds but --load never delivers the image locally, check for a Docker API version mismatch and set the override the docs describe, or push and pull instead of loading. Context: From the official Depot troubleshooting docs. A Docker API version mismatch between the client and the builder breaks depot build --load: the image builds but never loads into the local Docker.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

Tool: Docker. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

The docs list the workarounds: override the API version so client and server agree, or skip --load and use push/pull instead. The confusing part is that the build itself succeeds, so people blame their Dockerfile first.

Source: From the official Depot troubleshooting docs. A Docker API version mismatch between the client and the builder breaks depot build --load: the image builds but never loads into the local Docker. The docs list the workarounds: override the API version so client and server agree, or skip --load and use push/pull instead. The confusing part is that the build itself succeeds, so people blame their Dockerfile first.

Verified resolution: If depot build succeeds but --load never delivers the image locally, check for a Docker API version mismatch and set the override the docs describe, or push and pull instead of loading.

Source URL: https://github.com/depot/docs/blob/HEAD/content/container-builds/troubleshooting.mdx