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

当前回答

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

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

2)进入“设置”>重置

3)恢复出厂设置

其他回答

我正在使用窗口10,并执行以下步骤来解决此问题。

check虚拟化从任务管理器启用——>性能 重新启动docker服务 安装最新的docker版本并重新启动计算机。 确保docker服务正在运行。

以上步骤帮助我解决了这个问题。

如果您已经在启用Hyper-V的Windows 10 Pro上安装了docker,并且仍然不能在Windows 10上运行docker,那么,正如错误提示的那样,您的docker守护进程没有启动。

下面的步骤帮助我成功启动docker:

在cmd上使用命令(管理模式) docker-机器重启默认 然后你会收到这样一条消息: 用户打开C: \ \ \ {User_name} \ \ .docker \机\ \机器默认\ json: 系统无法找到指定的文件。 转到窗口托盘上的docker图标(桌面的右下角) 右键单击docker图标>设置>复位>重启docker 这要花点时间 然后你会看到下面的消息: Docker正在运行,指示灯为绿色

注意:如果您的系统上已经运行了Docker容器,那么请不要执行这些步骤。您可能会丢失现有的容器。

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

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

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

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

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

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

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

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

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