Docker桌面无法在启用WSL2的Windows 10中启动

时间:2020-11-05 19:24:36

标签: windows docker

Docker Desktop无法在启用WSL2的情况下启动,并且堆栈跟踪如下?任何帮助将不胜感激。

System.TimeoutException:
Timed out waiting for the lifecycle-server to start.
This may be the result of a slow environment or there may be a real problem.
This timeout can be increased by editing settings.json, value 'lifecycleTimeoutSeconds'.
This file is usually in C:\Users\(your username)\AppData\Roaming\Docker
   at Docker.ApiServices.LifecycleClient.<WaitForServerUpAsync>d__8.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\LifecycleClient.cs:line 84
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__25.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.Desktop\Engines\WSL2\LinuxWSL2Engine.cs:line 148
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\stable-2.5.x\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92

3 个答案:

答案 0 :(得分:1)

就我而言,帮助完全禁用了 Windows 10 专业版中的漏洞利用保护

  1. Windows 安全性
  2. 应用和浏览器控制
  3. 漏洞利用保护

如果您打算尝试,请同时检查 Program Settings 选项卡上 c:\Windows\System32\vmcompute.exe 进程的默认设置的覆盖。

答案 1 :(得分:0)

我遇到了同样的问题,并且按照错误中的说明解决了该问题。你尝试过吗?

长话短说,将lifecycleTimeoutSeconds中的C:\Users\(your username)\AppData\Roaming\Docker\settings.json设置从600更改为3600,然后重新启动Docker Desktop。

稍微研究一下问题以及应该设置的适当值,这个issue和这个comment特别有用。但从本质上讲,结论是错误消息具有所有内容,但要放入的实际值(3600和拥有它的精确文件(setttings.json)除外。

答案 2 :(得分:0)

就我而言,这是一个非常微不足道的问题:

docker 使用我唯一的 wsl2 发行版 (ubuntu),我也在终端中偶尔使用它,所以为了方便起见,我安装了 oh-my-zsh。一个简单的、未回答的“想要更新 oh-my-zsh?”提示阻塞了终端,不仅对我而且对 docker 也是如此。