Docker.Core.HttpBadResponseException: {"message":"2 errors occurred:\n\t* provisioning docker WSL distros: running wsl-bootstrap version set in main distro: exit status 1\n\t* checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found.\n\n"}

[Baolong-chao]

Docker.Core.HttpBadResponseException:
{"message":"2 errors occurred:\n\t* provisioning docker WSL distros: running wsl-bootstrap version set in main distro: exit status 1\n\t* checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found.\n\n"}

[JanEngelhardt]

Doing a wsl --update
and updating to the latest docker-desktop version fixed it for me.

[LeoChenZM]

I met the same issue, then I have ran the command 'wsl --update' and rebooted PC. The version of docker-desktop is also newest. But it doesn't work yet.

[onwike]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

[LeoChenZM]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role.
It's amazing, hope it will work for others.

[LedbetterBlog]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role. It's amazing, hope it will work for others.

Thank you very much for your method. I will write a blog to spread it！

[lmy54321]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role. It's amazing, hope it will work for others.

Thank you ,i met the same issue and fixed by your method.

[yodayuuki55]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role. It's amazing, hope it will work for others.

Thanks for your method, i fixed it after rebooting my machine.

[huyantao]

Thank you, i fixed it with your method.

[jamiematrix]

Got this issue a few hours ago. Had been working on a DDEV site fine and went to update WSL as there was an update available. Now getting the same error when Docker starts up.

I've restarted, run netsh winsock reset, checked wsl --update and as far as I know I have latest Docker installed.

I've tried to browse the directory the error is complaining about (\wsl$\docker-desktop-data) but cannot access it. I can get into \wsl$\docker-desktop and \wsl$\Ubuntu

[pangjunchi]

Thank you,I also fixed it

[poolye]

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role. It's amazing, hope it will work for others.

Thank you very much, It worked for me.

[GallopLin]

Thanks, i fixed the problem

[SimSonic]

Updated WSL.
Uninstalled Docker.
Uninstalled WSL + Hyper-V.
Rebooted.
Installed WSL + Hyper-V.
Installed latest Docker Desktop (4.17.1).
Rebooted.

I can see only \\wsl.localhost\docker-desktop, but there is no \\wsl.localhost\docker-desktop-data folder.

Nothing helps...

P. S. Switched to use Hyper-V instead of WSL 2.

[LaerteNF]

@LeoChenZM Can you attempt a wsl --shutdown as well and let me know what happens afterwards?

Ah, I fixed it at last. I found a very secret blog that tells me to run a command netsh winsock reset via CMD with admin role. It's amazing, hope it will work for others.

Thanks man! Worked for me! I was already giving up.

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

/lifecycle locked