在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 Desktop包含一个自我诊断工具,可以帮助您识别一些常见问题。运行自诊断工具前,请先找到com.docker. diagnostic .exe。通常安装在C:\Program Files\Docker\Docker\resources\ com.docker. diagnostic .exe中。

在Powershell中运行自诊断工具。

& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

该工具运行一套检查,并在每个检查旁边显示PASS或FAIL。如果有任何失败,它会在最后突出最相关的部分。

然后执行以下命令

& 'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon

其他回答

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

这是最终的解决方案。这对我很有用!!

1)在你的系统托盘中找到鲸鱼,然后右键单击

2)进入“设置”>重置

3)恢复出厂设置

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

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

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

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

我遇到过这样的问题几次,但每次都是因为我没有启动docker。 要解决这个问题,只需打开docker并等待它完成启动。

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

假设你在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命令。

祝你好运。