Ddev: In WSL2 ddev start fails at docker-credential-desktop.exe, "error listing credentials"

Created on 29 Jun 2020  路  7Comments  路  Source: drud/ddev

On a Finnish Windows 10 Pro, I went through the tutorial https://www.ddev.com/ddev-local/ddev-wsl2-getting-started/ and everything works, except when I run ddev start, I get:

docker.credentials.errors.StoreError: Credentials store docker-credential-desktop.exe exited with "error listing credentials - err: exit status 1, out: 'Elementti盲 ei l枚ydy.'".
Failed to start firsttest: failed to start ddev-ssh-agent: Failed to run docker-compose [-f /home/kari/.ddev/ssh-auth-compose.yaml -p ddev-ssh-agent up --build --force-recreate -d], err='exit status 255', stdout='', stderr='Creating volume "ddev-ssh-agent_dot_ssh" with default driver
Creating volume "ddev-ssh-agent_socket_dir" with default driver
Building ddev-ssh-agent
[13734] Failed to execute script docker-compose
Traceback (most recent call last):
File "site-packages/docker/credentials/store.py", line 80, in _execute
File "subprocess.py", line 411, in check_output
File "subprocess.py", line 512, in run
subprocess.CalledProcessError: Command '['/mnt/c/Program Files/Docker/Docker/resources/bin/docker-credential-desktop.exe', 'list']' returned non-zero exit status 1.
etc.

"Elementti盲 ei l枚ydy." is Finnish for "The element can't be found".

The distro is Ubuntu 20.04 LTS, Docker Desktop is 2.3.0.3.

Most helpful comment

Hi @karikaariainen - There was a version of Docker Desktop that created a bogus .docker/config.json, see https://github.com/docker/for-mac/issues/3785#issuecomment-517791470

I think you might have that. I imagine a docker reset to factory defaults would fix this, also perhaps editing your (host-side) ~/.docker/config.json.

All 7 comments

Hi @karikaariainen - There was a version of Docker Desktop that created a bogus .docker/config.json, see https://github.com/docker/for-mac/issues/3785#issuecomment-517791470

I think you might have that. I imagine a docker reset to factory defaults would fix this, also perhaps editing your (host-side) ~/.docker/config.json.

Oh, you might try just docker logout as well. Some versions of docker have had the most annoying habit of not being able to pull images while logged into hub.docker.com, and logging out solves it.

This happens when ddev is run from Windows, too (WSL2 switched off).

Solved by

D:\ddev\mysite>docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: myusername
Password:
Login Succeeded

Interesting to know. You might want to mention that on one of those other issues. Sounds like you got it working!

Note that you absolutely do not have to be logged into dockerhub to use ddev, everything is anonymous download. But you're definitely seeing a docker bug.

Somebody actually mentioned that in an other issue. Specifically logging in, not out. I'll see if this helps on WSL2, too.

Yep, sure does. Before logging in to Docker, ddev start fails on both WSL2-Ubuntu-ddev and Windows-ddev. After logging in, it works on both.

Thanks for sorting out this problem.

If I understand, the answer was "docker login and then docker logout again (logout is optional)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rickmanelius picture rickmanelius  路  4Comments

mfrieling picture mfrieling  路  7Comments

juergen-venne picture juergen-venne  路  7Comments

rvolk picture rvolk  路  4Comments

Gonzalo2683 picture Gonzalo2683  路  5Comments