search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.85k stars 289 forks source link

Docker will not start #13493

Open dmarquis-vail opened 1 year ago

dmarquis-vail commented 1 year ago

Actual behavior

Docker does not start. Docker was working just fine until updating to v4.18. That when this originally appeared. A complete reinstall worked until Docker was updated to v4.19 then it started happening again.

Expected behavior

Docker should start

Information

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

[2023-05-16T15:46:43.669524400Z][com.docker.diagnose.exe][I] set path configuration to OnHost Starting diagnostics [PASS] DD0027: is there available disk space on the host? [SKIP] DD0028: is there available VM disk space? [SKIP] DD0002: does the bootloader have virtualization enabled? [FAIL] panic: DD0018: does the host support virtualization? checking virtualization support via Windows service: Get "http://ipc/hyperv/check-virtualization": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:43.690597600Z][com.docker.diagnose.exe][I] ipc.NewClient: 3c6dec60-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service
[2023-05-16T15:46:43.690597600Z][com.docker.diagnose.exe][I] (39bcf59f) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /hyperv/check-virtualization
[2023-05-16T15:46:43.691828500Z][com.docker.diagnose.exe][W] (39bcf59f) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /hyperv/check-virtualization (1.2309ms): Get "http://ipc/hyperv/check-virtualization": open \.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-16T15:46:43.692662200Z][com.docker.diagnose.exe][I] (39bcf59f-1) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:43.693402200Z][com.docker.diagnose.exe][W] (39bcf59f-1) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (740┬╡s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:44.707468200Z][com.docker.diagnose.exe][I] (39bcf59f-2) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:44.709064500Z][com.docker.diagnose.exe][W] (39bcf59f-2) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (1.5963ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:45.717317900Z][com.docker.diagnose.exe][I] (39bcf59f-3) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:45.717890200Z][com.docker.diagnose.exe][W] (39bcf59f-3) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (860.7┬╡s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:46.730201100Z][com.docker.diagnose.exe][I] (39bcf59f-4) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:46.730909400Z][com.docker.diagnose.exe][W] (39bcf59f-4) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (708.3┬╡s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:47.742325400Z][com.docker.diagnose.exe][I] (39bcf59f-5) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:47.743589000Z][com.docker.diagnose.exe][W] (39bcf59f-5) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (1.2636ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:48.756354300Z][com.docker.diagnose.exe][I] (39bcf59f-6) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:48.757397600Z][com.docker.diagnose.exe][W] (39bcf59f-6) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (1.0433ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:49.772672600Z][com.docker.diagnose.exe][I] (39bcf59f-7) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:49.772987900Z][com.docker.diagnose.exe][W] (39bcf59f-7) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (315.3┬╡s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-16T15:46:50.786504800Z][com.docker.diagnose.exe][I] (39bcf59f-8) 3c6dec60-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-16T15:46:50.787487900Z][com.docker.diagnose.exe][W] (39bcf59f-8) 3c6dec60-com.docker.diagnose C<-S NoResponse GET /ping (983.1┬╡s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. runtime error: invalid memory address or nil pointer dereference [signal 0xc0000005 code=0x0 addr=0x1c1 pc=0x7699b1] goroutine 1 [running]: github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.findStringInKMSG({0xa4a6c0?, 0xc000008120?}) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/vm.go:55 +0x51 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.vmStartWorks({[FAIL] 0xc00038f8a0?DD0001: is the application running? Docker is not running , 0xc00038f8c0? }) C:\Program Files\Docker\Docker\resources> github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/vm.go:41 +0x25 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.(*test).GetResult(0xf5ea80, {0xa51028?, 0xc00049f7d0?}) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/test.go:47 +0x4f github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.Run.func1(0xf5ea80) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:21 +0x65 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x6?, 0xf5ea80) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:146 +0x77 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x5, 0xf5ea80, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:155 +0x87 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x4, 0xf5eb00, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:152 +0x52 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0xf5eb80, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:152 +0x52 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0xf5ec80, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:152 +0x52 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0xf5ed00, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:152 +0x52 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xf5f580, 0xc000445770) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:152 +0x52 github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.walkOnce(0xc0003df8c8?, 0xc0003df908) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:141 +0xcc github.com/docker/pinata/common/pkg/diagkit/gather/diagnose.Run({0xa51028, 0xc00049f7d0}, 0xf5f580, 0xc000062000?, 0x1) github.com/docker/pinata/common/pkg/diagkit/gather/diagnose/run.go:20 +0x213 main.checkCmd({0xc0000703d0?, 0xc0003dff50?, 0x2?}, {0x0, 0x0}) github.com/docker/pinata/common/cmd/com.docker.diagnose/main.go:157 +0x129 main.main() github.com/docker/pinata/common/cmd/com.docker.diagnose/main.go:119 +0x329

Steps to reproduce the behavior

  1. ...
  2. ...
dmarquis-vail commented 1 year ago

Anyone have any ideas? This keeps popping up every time Docker updates.

rfay commented 1 year ago

@dmarquis-vail - your system doesn't support virtualization, so you won't be able to use Docker Desktop. You have to figure out how to enable it in your environment (BIOS or whatever). It's giving you a clear message: "panic: DD0018: does the host support virtualization? checking virtualization support via Windows service: Get "http://ipc/hyperv/check-virtualization""

dmarquis-vail commented 1 year ago

@rfay I did see that message, virtualization is enabled. With a fresh install Docker works just fine up until it updates.

rfay commented 1 year ago

I guess I'd probably completely uninstall and look for things that didn't get uninstalled and then reinstall. (Per below, use WSL2!)

Oh, I also didn't see that you're using Hyper-V. Time to move to WSL2.. that's where the maintenance is happening. Highly recommended, far better.