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

当前回答

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

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

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

其他回答

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

选择一个

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 然后重新启动系统

我也有同样的问题。

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

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

在安装Windows 10之后,我也得到了同样的错误。我尝试重新启动,但它不工作,所以我做了以下(不建议如果你已经在docker工作了一段时间,这是在一个新的安装):

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

2)进入“设置”>重置

3)恢复出厂设置

然后我就可以按照网站上的docker入门教程使用Windows 10,现在它就像一个魅力。

我也遇到了同样的问题。我通过启用hyper-v解决了这个问题。

在BIOS中开启虚拟化 安装hyper - v

随着docker最近的更新,我有一个问题,docker应用程序在启动时挂起。我通过使用任务管理器终止wsl.exe来解决这个问题。