Fixing "err: docker-credential-desktop resolves to executable in current directory"

Docker Desktop
1

Attempting with a fresh install of Docker to docker-compose up --build a project but getting the error: error getting credentials - err: docker-credential-desktop resolves to executable in current directory (./docker-credential-desktop), out:

Docker compose is installed:

% docker-compose --version
Docker Compose version v2.18.1

I’ve seen various things around the net about the json config being incorrectly formatted, e.g. credsStore vs credStore:

{
        "credsStore": "Desktop",
        "auths": {},
        "credHelpers": {
                "https://index.docker.io/v1/": "desktop"
        },
        "currentContext": "desktop-linux"
}

Modifying that line, or removing it entirely makes no difference.

I have also seen recommendations to make sure I’m signed into desktop. I am signed in, and the account is verified.

Any ideas?

Currently:
Mac v11.6.1
Docker Desktop v4.20.1
Docker Compose v2.18.1

[resolved] Dealing with docker-credential-desktop resolves to executable in current directory (./docker-credential-desktop)
2

Got bitten by the same error message after having deinstalled a botched default Docker Desktop installation due to Docker never having heard of spaces in Windows paths and reinstalling. Afterwards, your dreaded error. In my case, a swift rm -rf ~/.docker cured the situation and I was then able to use “docker compose” without errors.

5 Likes
3

Thanks @halb0 this fixed it for me :slight_smile:

4

Fixed for me too, thanks

5

I had to create an account here just to thank you!

thank you!

6

@halb0 I also had to create an account here just to thank you!! You are a gentleman and scholar!! :grinning: :+1:

7

I only needed to delete ~/.docker/config.json because it had the creds config that wasn’t valid.

9

This helped me as well. Thank you.

For me, it seems that the ~/.docker directory was created by Docker Desktop which I had installed before this error. And though I had uninstalled it and switched to the default context, this config dir and files were still being used, hence the error.