issue: docker desktop failed to initialize

[2arch]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: F364A9FA-E8C2-4A24-AD76-FB9BB129B9C8/20221020211412

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

• Windows Version: 11
• Docker Desktop Version: latest
• WSL2 or Hyper-V backend? ?
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: just on my computer

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

[Tobion]

Same problem

[Juuldamen]

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.

[GijsCalis]

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.
Diagnostics ID: 067E9FD6-CAD6-43D2-86CA-171882389981/20221021153411

[viceice]

seeing same https://gist.github.com/viceice/ab813debab2040ea3eb6070d08a284d0

[pcaversaccio]

Experiencing the same problem - reinstalling didn't solve the problem

[ktzsolt]

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 and now I also have to move the whdx manually again to my other drive, because the new --installation-dir flag that is introduced in this release is not working. 🤬

"E:\Downloads\Docker Desktop Installer.exe" --installation-dir "D:\docker-desktop"

C:\Users\myuser>System.Exception: Unknown command --installation-dir
at: CommunityInstaller.InstallerSettings.ParseCommand(IList1 args) at: CommunityInstaller.InstallerSettings.FromArgs(IList1 args)
at: CommunityInstaller.Program.Run(String[] args)
at: CommunityInstaller.Program.Main(String[] args)

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

"Docker Desktop Installer.exe" install --installation-dir="D:\docker-desktop"

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.

[aboe026]

I'm seeing the same issue. Is there a way I can grab logs to help problem solve?

[nicks]

@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:

setting overrides for proxies: computing HTTPIP of 192.168.65.0/28: prefix of 28 does not accommodate a host numbered 128

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?

[viceice]

i don't have any proxy set. I've only a normal private ipv4 and public ipv6 address.

[lkt82]

Same problem

[jsidoruk]

Had the same issue, fixed by old workaround: delete or rename the folder %appdata%\Docker

[aboe026]

@nicks I don't think mine exited successfully:

C:\Program Files\Docker\Docker\resources>com.docker.diagnose.exe gather -upload
[2022-10-25T23:15:55.752859900Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Gathering diagnostics for ID 290F7888-E069-407B-A233-9E9FE9FE60A1/20221025231555 into C:\Users\adamb\AppData\Local\Temp\290F7888-E069-407B-A233-9E9FE9FE60A1\20221025231555.zip.
This may take up to 15 minutes.
time="2022-10-25T16:15:55-07:00" level=info msg="Triggering Linux sysrq and log flushes via a unix socket: \\\\.\\pipe\\dockerDiagnosticd" type=unixsock
time="2022-10-25T16:15:55-07:00" level=warning msg="/flush failed: Post \"http://unix/flush\": open \\\\.\\pipe\\dockerDiagnosticd: The system cannot find the file specified." type=unixsock
unable to trigger dns-forwarder diagnostics: Post "http://ipc/diagnostics": open \\.\pipe\dockerDnsForwarder: The system cannot find the file specified.
time="2022-10-25T16:16:02-07:00" level=info msg="Start gathering list of 126 elements (timeout=15m0s)" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering ProxyAPIGatherer" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering BackendGatherer" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering DiagKit" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering LifecycleServerGatherer" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering DiagKit took 3.5082ms" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Gathering system" type=list
time="2022-10-25T16:16:02-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ $(Get-WmiObject Win32_OperatingSystem) | ConvertTo-json -Depth 1 }]"
time="2022-10-25T16:16:04-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ $(Get-WmiObject Win32_ComputerSystem) | ConvertTo-json -Depth 1 }]"
time="2022-10-25T16:16:05-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ $(Get-WmiObject Win32_Processor) | ConvertTo-json -Depth 1 }]"
time="2022-10-25T16:16:07-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ $(Get-WmiObject Win32_BaseBoard) | ConvertTo-json -Depth 1 }]"
time="2022-10-25T16:16:08-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ Get-Item 'Registry::HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion' }]"
time="2022-10-25T16:16:09-07:00" level=info msg="Executing: [powershell -NoProfile -Command &{ Get-MpComputerStatus }]"
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering ProxyAPIGatherer took 7.0679312s" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering ProcessGatherer" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering LifecycleServerGatherer took 7.0689311s" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering typeperf \\Process(*)\\% Processor Time  (timeout 0s)-sc  (timeout 0s)5  (timeout 0s)-y" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Executing: [typeperf \\Process(*)\\% Processor Time -sc 5 -y]"
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering ProcessGatherer took 23.9994ms" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Gathering tasklist /V" type=list
time="2022-10-25T16:16:10-07:00" level=info msg="Executing: [tasklist /V]"
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
2022/10/25 16:16:11 exit status 0xffffffff

Here's the result of the check:

C:\Program Files\Docker\Docker\resources>com.docker.diagnose.exe check
[2022-10-25T23:17:05.227536700Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[FAIL] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 0xffffffff
[FAIL] DD0035: is the VM time synchronized? exit status 0xffffffff
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-25T23:17:10.311918200Z][com.docker.diagnose.exe][I] ipc.NewClient: 9f6133bc-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func14()
[       common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x8b
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x12f5080)
[       common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x12f5080)
[       common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x12f5080)
[       common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x12f5080, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x12f5100, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x12f5180, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x12f5900, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0xc83700?, 0xc00035f890)
[       common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x12f5900, 0xc65d9c2400000010?, {0xc00035fb20, 0x1, 0x1})
[       common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc00008a3d0?, 0xc00008a3d0?, 0x4?}, {0x0, 0x0})
[       common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[       common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-25T23:17:10.311918200Z][com.docker.diagnose.exe][I] (4cacd451) 9f6133bc-diagnose C->S diagnosticsd GET /ping
[2022-10-25T23:17:10.312416200Z][com.docker.diagnose.exe][W] (4cacd451) 9f6133bc-diagnose C<-S NoResponse GET /ping (498µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:10.313416200Z][com.docker.diagnose.exe][I] ipc.NewClient: 7ebb8e73-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[       linuxkit/pkg/desktop-host-tools/pkg/client/client.go:59
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0xd47baf, 0x13})
[       linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0x99
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[       common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x12f5100)
[       common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x12f5100)
[       common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x12f5100)
[       common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x12f5100, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x12f5180, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x12f5900, 0xc00038f728)
[       common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0xc83700?, 0xc00035f890)
[       common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x12f5900, 0xc65d9c2400000010?, {0xc00035fb20, 0x1, 0x1})
[       common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc00008a3d0?, 0xc00008a3d0?, 0x4?}, {0x0, 0x0})
[       common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[       common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-25T23:17:10.313916600Z][com.docker.diagnose.exe][I] (b6325b8a) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-10-25T23:17:10.313916600Z][com.docker.diagnose.exe][W] (b6325b8a) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:10.314416600Z][com.docker.diagnose.exe][I] (b6325b8a-1) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:10.314416600Z][com.docker.diagnose.exe][W] (b6325b8a-1) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:11.328574800Z][com.docker.diagnose.exe][I] (b6325b8a-2) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:11.328574800Z][com.docker.diagnose.exe][W] (b6325b8a-2) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:12.330252800Z][com.docker.diagnose.exe][I] (b6325b8a-3) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:12.330252800Z][com.docker.diagnose.exe][W] (b6325b8a-3) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:13.331962200Z][com.docker.diagnose.exe][I] (b6325b8a-4) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:13.331962200Z][com.docker.diagnose.exe][W] (b6325b8a-4) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:14.347663900Z][com.docker.diagnose.exe][I] (b6325b8a-5) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:14.348170400Z][com.docker.diagnose.exe][W] (b6325b8a-5) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (506.5µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:15.363295900Z][com.docker.diagnose.exe][I] (b6325b8a-6) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:15.363295900Z][com.docker.diagnose.exe][W] (b6325b8a-6) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:16.364485100Z][com.docker.diagnose.exe][I] (b6325b8a-7) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:16.364924500Z][com.docker.diagnose.exe][W] (b6325b8a-7) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-25T23:17:17.367503700Z][com.docker.diagnose.exe][I] (b6325b8a-8) 7ebb8e73-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-25T23:17:17.367503700Z][com.docker.diagnose.exe][W] (b6325b8a-8) 7ebb8e73-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
2022/10/25 16:17:17 exit status 0xffffffff

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?