cli commands pull/build getting stuck on auth with WSL2/docker-desktop

[patricknazar]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: CD7A79EC-80D6-4C8F-83B0-969B51F3B378/20200728071905

Expected behavior

Doesn't get stuck.

Actual behavior

Get's stuck.

Information

• Windows Version: Windows 10 2004 20175.1000
• Docker Desktop Version: 2.3.3.2 (46784) / Edge
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No? WSL2 with docker-desktop integration

Steps to reproduce the behavior

I can't reproduce but I can describe:

• docker -D pull or docker -D build hangs. Shows nothing that hints at the problem, just gets stuck.
• docker-compose --verbose build x gets stuck on docker.auth.resolve_authconfig: Using credentials store "desktop.exe" docker.auth._resolve_authconfig_credstore: Looking for auth entry for 'https://index.docker.io/v1/'

I thought I found a solution, I mentioned at docker-compose build hangs and mentioned at Unable to pull images with WSL2 engine
but not it was too good to be true. sgtoj on the second issue had a hanging problem I've tried signing in/out on docker-desktop, reinstalling, resetting to factory settings etc, nothing is working.

• docker-compose --verbose pull x where x is a service that has a image: xx property, Gets stuck in an infinite loop:

docker.auth.get_config_header: Looking for auth config
docker.auth.resolve_authconfig: Using credentials store "desktop.exe"
docker.auth._resolve_authconfig_credstore: Looking for auth entry for 'https://index.docker.io/v1/'
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
...

[stephen-turner]

There's a bug in the latest Windows Insiders build that stops Docker Desktop from working. See #7808.

[metcalfc]

This WSL2 bug microsoft/WSL#5648 does effect Docker, it is not an issue with Docker. We are hopeful for a fix soon. Right now Windows 20175 and 20180 have this issue. You can disable the WSL2 backend in your Docker settings for now. You won't find docker in your WSL2 path anymore but you can work around this temporarily with:

alias docker=docker.exe

Docker on the Windows side (powershell, cmd, etc) will behave normally.

[patricknazar]

I've just been deleting ~/.docker/config.json

[ducminhquan]

I've just been deleting ~/.docker/config.json

Removing ~/.docker/config.json seems to solve the issue, but it is re-created after restarting Docker or rebooting Windows.

[patricknazar]

Removing ~/.docker/config.json seems to solve the issue, but it is re-created after restarting Docker or rebooting Windows.

Yeah, so I put the rm command in .bashrc, a hack, but it's working out for now

UPDATE: my problem was fixed in issue 5648 of WSL deployed in windows 20190, I've since removed the entry in .bashrc

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked