在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>

当前回答

我解决这个问题的最简单的方法是终止docker桌面并重新启动它。如果您在左下角看到一个蓝色的docker图标,那么这意味着docker守护进程已经成功启动,上面的错误应该得到修复。

其他回答

如果你看到码头桌面是停止或不运行屏幕在左侧底部,然后执行以下操作

以管理员身份运行打开PowerShell 如果Docker Desktop是打开的,关闭它 在PowerShell上执行以下命令 " & 'C:\Program Files\Docker\ DockerCli.exe' -SwitchDaemon " 打开Docker Desktop,它将开始。

我正面临着这个问题。我尝试了上述的步骤,对我很有效。谢谢!

如果其他答案都不适合你,试试这个: 打开一个终端并运行:

wsl -l -v 

如果你注意到Docker -desktop仍然挂在“Installing”状态,关闭Docker,以管理员身份运行powershell并注销Docker -desktop:

PS C:\WINDOWS\system32> .\wslconfig.exe /u docker-desktop

重新启动docker,希望它能工作。如果没有,尝试先卸载docker,然后注销docker-desktop,重新安装docker。

来源:https://github.com/docker/for-win/issues/7295 # issuecomment - 645989416

我也有同样的问题。

启动docker守护进程解决了这个问题。只需搜索docker,按下windows键,然后点击“docker Dekstop”。Daemon应该马上就能运行了。

启动Docker Desktop后,确保左下角的Docker守护进程状态为绿色,并在鼠标悬停在其上时显示为RUNNING。

如果你用的是Windows,试试这个

 docker-machine env --shell cmd default 
 @FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

进行测试

docker run hello-world

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

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进行测试。