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

当前回答

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

假设你在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的docker, OS Built 19042和版本20H2,如这个视频所示, 但我的docker还在起步阶段。我用提供的命令运行docker,但我得到了这样一个 连接时错误:Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version: open //。/pipe/docker_engine:系统找不到文件

然后,这些解决方案为我启动docker工作:

以管理员身份打开Powershell & 运行这个命令:'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon

OR

以管理员身份打开cmd & 运行命令:"C:\Program Files\Docker\Docker\DockerCli.exe

我在这里找到了这个。希望这对你也有帮助!

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

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

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

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

原因:其中一个原因可能是由于命令关闭了vmmem

wsl --shutdown

解决方案:通过右键单击重新启动Docker将解决问题。

我也有同样的问题。

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

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

遇到类似的问题,在运行在WSL2上的Windows虚拟机上安装了docker桌面。

解决方案:

更新Windows到最新版本,VMTools到最新(11.2)版本,修复了这个问题,现在docker正在不停地运行。