My docker desktop was upgraded to 4.32.0. After upgradation, I started receiving the following error when restarting it.
The problem persists even after several restarts.
deploying WSL2 distributions ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: open \wsl$\docker-desktop\etc\wsl_bootstrap_version: The network name cannot be found. checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The network name cannot be found
*
docker version
Client:
Version: 27.0.3
API version: 1.46
Go version: go1.21.11
Git commit: 7d4bcd8
Built: Sat Jun 29 00:03:32 2024
OS/Arch: windows/amd64
Context: default
docker info
Client:
Version: 27.0.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.15.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.28.1-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.32
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.14
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.25
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.10.0
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Additional Info
Windows OS
Edition Windows 11 Pro
Version 23H2
Installed on 03/06/2024
OS build 22631.3737
Experience Windows Feature Experience Pack 1000.22700.1009.0
I got the exact same issue on the exact same Docker version upgrade as you did. I tried multiple things I’ve found, but the following was successful for me:
Try the following:
Stop Docker Desktop
Run the following command in your terminal wsl --unregister docker-desktop
Run Docker Desktop again (Will recreate the distro)
Note: I also start my Docker Desktop as Administrator each time, so you probably need to run your terminal/Powershell as Administrator like I did.
off topic, but this is not the first time I update my docker then failed in various way, can docker team do a proper testing before publicise the update? Something like safe version? Beta version? Alpha version?
One of my colleague found to start docker desktop with normal user (ignore admin user) . It works for me as well in this way. Strange behaviour and unfortunately, I don’t understand this. @amg31@imagineuserfordocker
Exact same problem for me. Running “wsl --unregister docker-desktop” has gotten me past the problem as well.
I’d like to add to the sentiment that Docker Desktop is one of the worst-performing and trouble-causing applications on my development machine. I don’t think there’s another app I’ve encountered that so consistently stops working and requires serious debugging and troubleshooting time in order to get it working again.
This is still happening after upgrade to 4.33.1. I’d hoped it would be fixed. I’m pretty sure it’s screwing up, or the hacky “fix” is screwing up my persistent volumes - they are getting wiped out every time I restart my machine and have to restart Docker Desktop.
I will start a new topic because it’s obvious no one from Docker is paying attention to this one. They certainly aren’t doing anything about this bug.
