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

当前回答

当你得到这个错误时,你可以启动Kitematic。它将显示一个按钮来重置虚拟机,并将修复问题。

其他回答

对我来说,这个错误是通过停止在Hyper-V中运行的虚拟Ubuntu实例来解决的:

系统无法找到指定的文件。在Windows上的默认守护进程配置中,docker客户端必须以提升方式运行才能连接。此错误也可能表明docker守护进程没有运行。

一旦Ubuntu实例停止,Docker Desktop重新启动,我通常使用的Docker命令就可以正常运行了。

PS:我之所以有这个想法是因为Docker Desktop已经编译了一个错误日志,并提供了作为用户反馈发送到Docker Hub…日志似乎表明我的机器内存不足,Docker失败的原因很简单。杀死Ubuntu实例解决了这个问题。

您需要管理员权限来运行该服务

我也遇到过类似的问题。当我运行命令提示符(以管理员身份运行)并输入“docker版本”时,问题就消失了。

C:\WINDOWS\system32>docker version


Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:23:10 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:29:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

我知道这个问题是很久以前的问题了,但我没有找到合适的解释和解决方案,所以希望我的答案是有用的:)

假设你在Windows上安装了Docker工具箱,Docker和Docker -machine命令都是可用的。通常,人们在使用这两种方法时都会感到困惑。

docker命令仅在虚拟机中用于管理映像。docker-machine命令用于在主机上管理Linux虚拟机。

所以,请在您的Windows机器上使用docker-machine命令。在虚拟机内部使用docker命令。要使用docker命令,例如docker ps,您可以打开docker快速启动终端,或者在cmd/bash/PowerShell上运行这些命令:

docker-machine run default /假设default是你的Linux虚拟机/

Docker-machine SSH默认

这将启动boot2docker,您将在命令行上看到docker图标。然后可以使用docker命令。

祝你好运。

对我来说,问题是虚拟化没有启用。

在windows 10上:进入任务管理器->性能-> CPU,你应该看到“虚拟化:已启用”部分

如果您没有看到此选项,则意味着尚未启用虚拟化。

另一个要注意的有趣的事情是你必须启用Hyper V。然而,当我使用并行桌面时,我必须启用“嵌套虚拟化”,以使Hyper V“真正启用”。因此,如果您的windows是一个虚拟机,请检查Parallels(或任何您正在使用的)的设置,以启用嵌套虚拟化。

我在Docker 19.03.12版和Windows 10版上得到了同样的错误。通过以下步骤解决这个问题。希望它能帮助别人。

Go to Windows Start -> Search Box (Type here to search). There enter 'Services'. Among the listed items, click Services app. Now search 'Docker Desktop Service' in the Services window opened. Right click on it and Start the service. Its status should be changed to 'Running'. If step 2 gives error like 'the dependency service failed to start', then start all dependency services. For me, I had to start a service called 'Server'. Double click 'Docker Desktop' icon in desktop. Now you will see 'Docker Desktop is running' in system tray. Now run the command 'docker version' from Command Prompt or PowerShell. It should give clean output. If any issue in step 5, run Command Prompt or PowerShell as administrator.

上述解决方案假设Docker已经安装,并且在您的系统中启用了Hyper-V / Virtualization。