issue: docker desktop failed to initialize #13025
Comments
|
Same problem |
|
Same issue after updating to the latest version Edit: was able to resolve it by uninstalling & installing version 4.13.0. But you will lose your local images by doing this.
|
|
Reinstalling 4.13.0 did not work for me, reinstalling 4.12.0 did work luckily. All images and containers are still there for me (using WSL, not Hyper-V). I also uploaded Diagnostics. Gathered after reinstalling 4.12.0, but logfiles include the problematic 4.13.0 installation with backend apparently in some sort of restart loop. |
|
Experiencing the same problem - reinstalling didn't solve the problem |
|
Same here. My docker-desktop WSL2 distro is gone after trying to update to 4.13.0. When I ran "wsl -l -v" I only had the docker-desktop-data. Uninstalling and reinstalling solved the issue, except I lost all my images, extensions, configs
I should have had rtfm about cli installation: https://docs.docker.com/desktop/install/windows-install/#install-from-the-command-line. After installing with the correct params
DD is stuck in "starting" phase. It still put the vhdx in C:\Users\myuser\AppData\Local\Docker\wsl\data regardless of the installation-dir flag. |
|
I'm seeing the same issue. Is there a way I can grab logs to help problem solve? |
|
@aboe026 Posting a diagnostic ID is always helpful. https://docs.docker.com/desktop/troubleshoot/overview/ The diagnostics posted above were really helpful thanks. A few of them have the line from @viceice's github link: and the network engineers think it's a proxy networking issue. if you have a proxy set, can you try replacing /28 with /24 and see if that helps? |
|
i don't have any proxy set. I've only a normal private ipv4 and public ipv6 address. |
|
Same problem |
|
Had the same issue, fixed by old workaround: delete or rename the folder %appdata%\Docker |
|
@nicks I don't think mine exited successfully: Here's the result of the check: When I try to start Docker again (after having restarted my computer after getting the initial error), nothing seems to happen -- I don't get the error message again, no Docker icon shows in my system tray. @jsidoruk , does that method result in data loss? |
|
Fixed: |
|
@GijsCalis thanks for the diagnostic -- I spotted an error in your logs which is due to a lack of parameter validation and lack of upgrade logic in that build. Would you be able to try a developer build? https://desktop-stage.docker.com/win/main/amd64/90037/Docker%20Desktop%20Installer.exe On upgrade it will look at the It will also validate the setting correctly in the UI. Let me know if that helps. If not, could you upload another diagnostic? @rtman238 I think this explains why deleting that folder made it work -- the default |
|
ha, never changed the subnet, but here it's a 28: "useVpnkit": true,
"useWindowsContainers": false,
"vpnKitMaxPortIdleTime": 300,
"vpnKitTransparentProxy": false,
"vpnkitCIDR": "192.168.65.0/28",
"wslEnableGrpcfuse": false,
"wslEngineEnabled": truewould a manual change fix the issue too? (while docker is stopped of cause) |
|
it seems to work now. needed to stop docker once again after auto update. |
Successfully updated using dev build 1.14.0 90037.
After restarting Windows all was well and Docker Desktop is working OK. Diag after installation: Diagnostics ID: 067E9FD6-CAD6-43D2-86CA-171882389981/20221026152050 |
|
I manually changed the |
|
Fix of @aboe026 works for me too |
|
I have nearly the same output from running the My settings.json also has that |
I got the same problem after upgrading to Docker Desktop 4.13.1 (90346), this solution works for me, thanks @aboe026 |
|
The vpnkit networking issue reported here is fixed in 4.13.1 |
I also had this problem when updating from 4.12 directly to 4.13.1 and after changing |
|
Same as @LepkoQQ, Docker Desktop auto-updated overnight and then would not start. I never modified any subnet settings in the GUI, but manually editing |
|
For anyone else finding this issue the fix above worked for me too and the location of |
|
Fix has been released in Docker Desktop 4.14.0. See release notes for more details. |
|
This latest debacle demonstrated clearly that at minimum, when a user uninstalls Docker Desktop, that the uninstaller should ask the user whether they want to keep all their settings/data in case they want to reinstall later. |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
and others
Actual behavior
Docker Desktop failed to initialize Docker Desktop shutting down
Hardware assisted virtualization and data execution protection must be enabled in the BIOS. See https://docs.docker.com/desktop/windows/troubleshoot/#virtualization
Expected behavior
Docker Desktop runs
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" checkThe text was updated successfully, but these errors were encountered: