window 无法访问docker,无法在Windows上启动Docker

最新推荐文章于 2025-06-23 15:43:57 发布

程序媛的那些事儿

最新推荐文章于 2025-06-23 15:43:57 发布

阅读量1.3k

点赞数

文章标签： window 无法访问docker

本文详细描述了解决Windows 10中Docker启动错误，涉及Hyper-V问题，步骤包括检查Virtual Machine Management服务和启用控制流保护。最终通过重启和管理员权限操作解决了问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

I continue to get the following error when trying to start docker on Windows 10 pro. my HyperV is turned on and running:

Version 18.04.0-ce-win62 (17151)

Channel: edge

e0a85f6

Any help would be appreciated!

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'C001715587' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.

at New-Switch, : line 117

at , : line 394

at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36

at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 75

at Docker.Actions.<>c__DisplayClass15_0.b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 59

at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

解决方案Open Windows Security

Open App & Browser control

Click Exploit protection settings

Switch to Program settings tab

Locate C:\WINDOWS\System32\vmcompute.exe in the list and expand it

Click Edit

Scroll down to Control flow guard (CFG) and uncheck Override system settings

Start vmcompute from powershell net start vmcompute (or alternately start the Hyper-V Host Compute Service from the system Services app)

Restart PC

Open Hyper-V as Administrator

Connect to Server, Local computer, OK

The above worked for me. I couldn't run docker, then I realized I couldn't connect to my local machine on hyper-v. I kept reading suggestions to reinstall hyper-v and do some restarts but this is what finally worked.