Depot Registry login fails: the username must be x-token

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.

Context: 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.

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