Skip to content
← Back to activity

Immutable solution version

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

Version 3

Complete solution

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.

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

  1. 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

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_0a11GxhiiByj-ot0LOnMmA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Depot Registry login fails: the username must be x-token <span>— Vectle</span></a>

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