在Windows上执行docker version命令返回的结果如下:

C:\Projects> docker version
Client:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   d8d3314
 Built:        Tue Nov  1 03:05:34 2016
 OS/Arch:      windows/amd64
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/version: open //./pipe/docker_engine: The system cannot find the file
specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

运行诊断将产生以下结果:

C:\Projects> wget https://github.com/Microsoft/Virtualization- 
Documentation/raw/master/windows-server-container-tools/Debug- 
ContainerHost/Debug-ContainerHost.ps1 -UseBasicParsin | iex

Checking for common problems
Describing Windows Version and Prerequisites
 [+] Is Windows 10 Anniversary Update or Windows Server 2016 608ms
 [+] Has KB3192366, KB3194496, or later installed if running Windows build 14393 141ms
 [+] Is not a build with blocking issues 29ms
Describing Docker is installed
 [-] A Docker service is installed - 'Docker' or 'com.Docker.Service'  134ms
   Expected: value to not be empty
   27:         $services | Should Not BeNullOrEmpty
   at <ScriptBlock>, <No file>: line 27
 [+] Service is running 127ms
 [+] Docker.exe is in path 2.14s
Describing User has permissions to use Docker daemon
 [+] docker.exe should not return access denied 42ms
Describing Windows container settings are correct
 [-] Do not have DisableVSmbOplock set to 1 53ms
   Expected: {0}
   But was:  {1}
   66:              $regvalue.VSmbDisableOplocks | Should Be 0
   at <ScriptBlock>, <No file>: line 66
 [+] Do not have zz values set 42ms
Describing The right container base images are installed
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/images/json: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
 [-] At least one of 'microsoft/windowsservercore' or 'microsoft/nanoserver' should be installed 129ms
   ValidationMetadataException: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
   ParameterBindingValidationException: Cannot validate argument on parameter 'Property'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
   at <ScriptBlock>, <No file>: line 90
Describing Container network is created
 [-] Error occurred in Describe block 1.08s
   RuntimeException: Cannot index into a null array.
   at <ScriptBlock>, <No file>: line 119
Showing output from: docker info

Showing output from: docker version
Client:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   d8d3314
 Built:        Tue Nov  1 03:05:34 2016
 OS/Arch:      windows/amd64

Showing output from: docker network ls

Warnings & errors from the last 24 hours
Logs saved to C:\Projects\logs_20161107-084122.csv
C:\Projects>

当前回答

错误与这部分有关:

在Windows上的默认守护进程配置中,docker客户端必须 被提升运行连接

首先,验证Docker Desktop应用程序正在运行。如果没有,启动它:这将运行docker守护进程(只需等待几分钟)。 然后,如果错误仍然存在,您可以尝试切换Docker守护进程类型,如下所示:

Powershell:

以管理员身份打开Powershell 启动命令:& 'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon .exe

或者,使用cmd:

以管理员身份打开cmd 启动命令:“C:\Program Files\Docker\Docker\DockerCli.exe”-SwitchDaemon

其他回答

确保您以“管理员”身份启动Powershell,这也将防止您从docker版本中得到的错误。

到2021年,这些提示可能会过时:

然后尝试启动docker服务:start-service docker 如果失败,删除docker。Pid文件,你可以在CD $env:programfiles\docker;rm docker.pid 最后,您应该将HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Containers\VSmbDisableOplocks更改为0或删除该值。

在安装了带有WSL 2后端运行的Docker Desktop 4.7.1后,我在终端上也遇到了同样的问题。托盘鲸的图标也没有显示。

在我的情况下,问题是我之前已经安装了一个WSL发行版(Ubuntu),它已经是默认的。带有WSL 2后端的Docker Desktop安装了自己的发行版Docker - Desktop。并且它必须是默认的(至少在没有在其他地方配置的情况下)。

所以我不得不在PowerShell中运行这个命令:wsl——setdefault docker-desktop并重新启动docker服务。在这里找到了解决方案。

尝试用以下选项之一解决问题:

选择一个

Start-Service "Hyper-V Virtual Machine Management"
Start-Service "Hyper-V Host Compute Service"

or

选项B

打开“窗口安全” 打开“应用程序和浏览器控件” 点击底部的“利用保护设置” 切换到“程序设置”页签 在列表中找到“C:\WINDOWS\System32\vmcompute.exe”并展开它 点击“编辑” 向下滚动到“代码流保护(CFG)”,取消选中“覆盖系统设置” 从powershell“net Start vmcompute”启动vmcompute 然后重新启动系统

我的一个朋友也有类似的问题,我们尝试了一下,效果很好。

Hyper-V,尽管在“打开或关闭Windows功能”中被列为活动,但实际上并不是活动的。当在PowerShell下运行systeminfo时,这变得很明显,并且看到 要求被列出为满足(这不是您期望的Hyper-V实际运行的输出)。步骤:

打开“打开或关闭Windows功能” 如果您不确定如何做到这一点,请参考 https://www.howtogeek.com/250228/what-windows-10s-optional-features-do-and-how-to- [turn-them-on-or-off /] [1] 关闭Hyper-V(取消复选框,确保所有子组件都被标记为关闭) 点击“Ok”-你的机器将重新启动。 当你的电脑再次启动时,打开“打开或关闭Windows功能”,然后重新打开Hyper-V。您的机器将重新启动。

现在你可以通过运行docker hello-world image进行测试。

原因:其中一个原因可能是由于命令关闭了vmmem

wsl --shutdown

解决方案:通过右键单击重新启动Docker将解决问题。