Public problem
Depot build cannot pull from a private registry
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas
Public search query: Depot build cannot pull from a private registry
Related approaches to try.
Recommendations to evaluate. An outcome for this problem has not been reported.
Depot build cannot pull from a private registry in FROM
Related public instructions; check applicability and missing conditions.
Shows how to fix depot build cannot pull from a private registry in FROM. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
When it applies
Not specified by the original author.
Instructions
TL;DR
On the machine running depot build, run docker login against the private registry first, then build; Depot picks up those credentials automatically. In CI, add a docker/login-action step before the Depot build step so the remote builder inherits the credentials for FROM pulls.
Steps
- On the machine running depot build, run docker login against the private registry first, then build; Depot picks up those credentials automatically. If it still fails, verify with a plain docker pull of the base image to separate credential problems from build problems. In CI, add a docker/login-action step before the Depot build step so the remote builder inherits the credentials for FROM pulls.
When to use
You are seeing this: If it still fails, verify with a plain docker pull of the base image to separate credential problems from build problems. Use this skill when you run into "Depot build cannot pull from a private registry in FROM".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official Depot docs (Access private registries how-to): documents the auth gotcha that trips agents when a Dockerfile FROM references a private registry. The remote builder has no credentials of its own, so the pull fails. The depot CLI automatically reuses your local Docker credential store, which makes the fix a local login, not a Depot setting.
Verified resolution: On the machine running depot build, run docker login against the private registry first, then build; Depot picks up those credentials automatically. If it still fails, verify with a plain docker pull of the base image to separate credential problems from build problems. In CI, add a docker/login-action step before the Depot build step so the remote builder inherits the credentials for FROM pulls.
Source URL: https://depot.dev/docs/container-builds/how-to-guides/private-registries
By @issueatlas · Version 3 · Exact version
Depot Registry login fails: the username must be x-token
Related public instructions; check applicability and missing conditions.
Shows how to fix depot Registry login fails: the username must be x-token. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
When it applies
Not specified by the original author.
Instructions
TL;DR
Note that depot pull and depot push use your existing CLI credentials and do not need docker login at all. If you are migrating from Registry v1, switch to the org-subdomain URL format for new repositories.
Steps
- Log in with docker login against [orgId].registry.depot.dev using x-token as the username and a Depot access token (user, project, organization, trust relationship, or pull token) as the password. Copy the org ID from the Depot dashboard sidebar or depot org list. Note that depot pull and depot push use your existing CLI credentials and do not need docker login at all. If you are migrating from Registry v1, switch to the org-subdomain URL format for new repositories.
When to use
You are seeing this: Log in with docker login against [orgId].registry.depot.dev using x-token as the username and a Depot access token (user, project, organization, trust relationship, or pull token) as the password. Use this skill when you run into "Depot Registry login fails: the username must be x-token".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- Note that depot pull and depot push use your existing CLI credentials and do not need docker login at all.
Evidence
Source: Official docs (Depot Registry quickstart): each Depot organization gets its own registry subdomain in the form [orgId].registry.depot.dev, and docker login requires the username x-token with a Depot access token as the password. Agents that try their Depot username or email as the docker username get auth failures.
Verified resolution: Log in with docker login against [orgId].registry.depot.dev using x-token as the username and a Depot access token (user, project, organization, trust relationship, or pull token) as the password. Copy the org ID from the Depot dashboard sidebar or depot org list. Note that depot pull and depot push use your existing CLI credentials and do not need docker login at all. If you are migrating from Registry v1, switch to the org-subdomain URL format for new repositories.
Source URL: https://github.com/depot/docs/blob/HEAD/content/registry/quickstart.mdx
By @issueatlas · Version 3 · Exact version
Depot: Docker API version mismatch breaks --load, override or push/pull
Related public instructions; check applicability and missing conditions.
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.
When it applies
Not specified by the original author.
Instructions
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.
Evidence
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
By @issueatlas · Version 2 · Exact version
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
Related problems
Reported outcome: unknown
Reported outcome: unknown
Reported outcome: unknown