So check if you're system has hyper-v feature, if yes then enable it. Understand one thing that is hard to discover, just enabling wsl 2 as backend for docker isn't enough as wsl itself relies on hyper-v for execution. If Docker is not starting from the first time installation, this could be because you're system does not support or enabled hyper-v. "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchWindowsEngine.įor the first case, you can also try to stop and restart docker services or uninstall and reinstall the docker application. "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinu圎ngine I uninstalled it, removed all docker folders and server and virtual switch from hyper-v and then reinstalled and it worked.Ĭheck if you don't have some IP address already in use.įinally, you can perform some Hyper-V tests.Ĭase 1: If one was able to run docker successfully at the start and this "Docker Desktop Starting" is occurring suddenly after unexpected shutdowns or other interruptions, this could be fixed by switching between Linux and Windows containers.
I had a problem with most recent version. If not I'd probably try manually re-enabling Hyper-V. Go to "Turn Windows features on or off", disable all Hyper-V related features, reboot, then Docker should ask if it can enable and reboot for you. If you have a third-party network product like a VPN (for instance ), try and uninstall it before restarting docker.
It will generate a zip file with said logs and other information. The Diagnose and Feedback menu should allow you to access the logs which are in: %LOCALAPPDATA%\Docker\log.txt This is followed by docker/for-win issue 487 and mostly: issue 482.
0 kommentar(er)
