Advertisement
Guest User

Untitled

a guest
Nov 7th, 2022
173
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.00 KB | None | 0 0
  1. [PASS] DD0027: is there available disk space on the host?
  2. [SKIP] DD0028: is there available VM disk space?
  3. [PASS] DD0002: does the bootloader have virtualization enabled?
  4. [SKIP] DD0018: does the host support virtualization?
  5. [PASS] DD0001: is the application running?
  6. [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
  7. [PASS] DD0021: is the WSL 2 Windows Feature enabled?
  8. [FAIL] DD0024: is WSL installed? exit status 1
  9. [FAIL] DD0025: are WSL distros installed? exit status 1
  10. [PASS] DD0026: is the WSL LxssManager service running?
  11. [FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? context deadline exceeded
  12. [FAIL] DD0035: is the VM time synchronized? exit status 1
  13. [PASS] DD0017: can a VM be started?
  14. [PASS] DD0016: is the LinuxKit VM running?
  15. [FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: Das System kann die angegebene Datei nicht finden.
  16. [2022-11-07T11:03:48.476156300Z][com.docker.diagnose.exe][I] ipc.NewClient: 47e09413-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
  17. [common/pkg/diagkit/gather/diagnose.glob..func14()
  18. [ common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x8b
  19. [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1365080)
  20. [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
  21. [common/pkg/diagkit/gather/diagnose.Run.func1(0x1365080)
  22. [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
  23. [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x1365080)
  24. [ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
  25. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1365080, 0xc000491728)
  26. [ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
  27. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1365100, 0xc000491728)
  28. [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
  29. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1365180, 0xc000491728)
  30. [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
  31. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1365900, 0xc000491728)
  32. [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
  33. [common/pkg/diagkit/gather/diagnose.walkOnce(0xcf3700?, 0xc00035f890)
  34. [ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
  35. [common/pkg/diagkit/gather/diagnose.Run(0x1365900, 0xb414688b00000010?, {0xc00035fb20, 0x1, 0x1})
  36. [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
  37. [main.checkCmd({0xc0000803d0?, 0xc0000803d0?, 0x4?}, {0x0, 0x0})
  38. [ common/cmd/com.docker.diagnose/main.go:133 +0x105
  39. [main.main()
  40. [ common/cmd/com.docker.diagnose/main.go:99 +0x287
  41. [2022-11-07T11:03:48.476470300Z][com.docker.diagnose.exe][I] (9fd79fdc) 47e09413-diagnose C->S diagnosticsd GET /ping
  42. [2022-11-07T11:03:48.476470300Z][com.docker.diagnose.exe][W] (9fd79fdc) 47e09413-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: Das System kann die angegebene Datei nicht finden.
  43.  
  44. [FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  45. [2022-11-07T11:03:48.478008000Z][com.docker.diagnose.exe][I] ipc.NewClient: 8d1f8f9d-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
  46. [linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
  47. [ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:59
  48. [linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0xdb7baf, 0x13})
  49. [ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0x99
  50. [common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
  51. [ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
  52. [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1365100)
  53. [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
  54. [common/pkg/diagkit/gather/diagnose.Run.func1(0x1365100)
  55. [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
  56. [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x1365100)
  57. [ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
  58. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1365100, 0xc000491728)
  59. [ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
  60. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1365180, 0xc000491728)
  61. [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
  62. [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1365900, 0xc000491728)
  63. [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
  64. [common/pkg/diagkit/gather/diagnose.walkOnce(0xcf3700?, 0xc00035f890)
  65. [ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
  66. [common/pkg/diagkit/gather/diagnose.Run(0x1365900, 0xb414688b00000010?, {0xc00035fb20, 0x1, 0x1})
  67. [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
  68. [main.checkCmd({0xc0000803d0?, 0xc0000803d0?, 0x4?}, {0x0, 0x0})
  69. [ common/cmd/com.docker.diagnose/main.go:133 +0x105
  70. [main.main()
  71. [ common/cmd/com.docker.diagnose/main.go:99 +0x287
  72. [2022-11-07T11:03:48.478545300Z][com.docker.diagnose.exe][I] (225c838e) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /docker
  73. [2022-11-07T11:03:48.478545300Z][com.docker.diagnose.exe][W] (225c838e) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  74. [2022-11-07T11:03:48.478545300Z][com.docker.diagnose.exe][I] (225c838e-1) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  75. [2022-11-07T11:03:48.479062600Z][com.docker.diagnose.exe][W] (225c838e-1) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (517.3µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  76. [2022-11-07T11:03:49.480273800Z][com.docker.diagnose.exe][I] (225c838e-2) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  77. [2022-11-07T11:03:49.480273800Z][com.docker.diagnose.exe][W] (225c838e-2) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  78. [2022-11-07T11:03:50.481700600Z][com.docker.diagnose.exe][I] (225c838e-3) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  79. [2022-11-07T11:03:50.482211600Z][com.docker.diagnose.exe][W] (225c838e-3) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  80. [2022-11-07T11:03:51.483265500Z][com.docker.diagnose.exe][I] (225c838e-4) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  81. [2022-11-07T11:03:51.483265500Z][com.docker.diagnose.exe][W] (225c838e-4) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  82. [2022-11-07T11:03:52.484677400Z][com.docker.diagnose.exe][I] (225c838e-5) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  83. [2022-11-07T11:03:52.484677400Z][com.docker.diagnose.exe][W] (225c838e-5) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  84. [2022-11-07T11:03:53.485515500Z][com.docker.diagnose.exe][I] (225c838e-6) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  85. [2022-11-07T11:03:53.485515500Z][com.docker.diagnose.exe][W] (225c838e-6) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  86. [2022-11-07T11:03:54.486981600Z][com.docker.diagnose.exe][I] (225c838e-7) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  87. [2022-11-07T11:03:54.486981600Z][com.docker.diagnose.exe][W] (225c838e-7) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  88. [2022-11-07T11:03:55.487637600Z][com.docker.diagnose.exe][I] (225c838e-8) 8d1f8f9d-com.docker.diagnose C->S VMDockerdAPI GET /ping
  89. [2022-11-07T11:03:55.487796500Z][com.docker.diagnose.exe][W] (225c838e-8) 8d1f8f9d-com.docker.diagnose C<-S NoResponse GET /ping (158.9µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: Das System kann die angegebene Datei nicht finden.
  90.  
  91. [PASS] DD0015: are the binary symlinks installed?
  92. [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: Das System kann die angegebene Datei nicht finden.
  93. [PASS] DD0013: is the $PATH ok?
  94. 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: Das System kann die angegebene Datei nicht finden.
  95. [FAIL] DD0003: is the Docker CLI working? exit status 1
  96. [PASS] DD0005: is the user in the docker-users group?
  97. 2022/11/07 12:04:00 exit status 1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement