docker-credential-desktop Docker Origin: Platform & cloud OSI layer 7 · Application Last updated 12 Oct 2026

error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATH

~/.docker/config.json tells Docker to use a credential helper (desktop, osxkeychain, wincred) that isn’t installed or on PATH.

Exact message you may see error getting credentialsexecutable file not found in $PATH
Seen on: Docker

Meaning

After uninstalling Docker Desktop, switching to Colima/OrbStack, or in WSL, config.json still says "credsStore": "desktop", so every pull/login fails before contacting the registry.

Common causes

  • Docker Desktop removed but its credsStore setting left behind
  • Using Colima/Rancher/WSL with Desktop’s config
  • Helper binary not on PATH in CI/sudo

⚡ Quick fix

  1. Remove the "credsStore" line from ~/.docker/config.json
  2. Or install the matching docker-credential-* helper
  3. Log in again

Detailed fix by platform

Shell

  1. bash
    cat ~/.docker/config.json
    # delete: "credsStore": "desktop"   then
    docker login

How to diagnose

  1. Config — credsStore/credHelpers in ~/.docker/config.json
  2. Helper — which docker-credential-desktop

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

1046 — MySQL ERROR 1046 (3D000): No database selected (MySQL)10461049 — MySQL ERROR 1049 (42000): Unknown database 'x' (MySQL)10491153 — MySQL ERROR 1153 (08S01): Got a packet bigger than 'max_allowed_packet' bytes (MySQL)11533D000 — FATAL: database "x" does not exist (PostgreSQL)3D000413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413AADSTS50126 — AADSTS50126: Error validating credentials due to invalid username or password (Azure)AADSTS50126AADSTS90002 — AADSTS90002: Tenant 'x' not found (Azure)AADSTS90002api_version_invalid — API Error: Invalid or unsupported API version (API)api_version_invaliddocker-cr…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.