Docker无法在Windows上启动

在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-machine env --shell cmd default 
 @FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

进行测试

docker run hello-world

2018-01-26 13:09:04

其他回答

错误代码:

连接过程中出现错误:Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.29/version:开放 / /。/pipe/docker_engine:系统找不到指定的文件。在 Windows上的默认守护进程配置，必须运行docker客户端抬高连接。此错误也可能表明docker Daemon未运行。

解决方案:

1)对于Windows 7命令窗口(cmd.exe)，以管理员身份打开cmd.exe，执行如下命令:

docker-machine env --shell cmd default

您将收到以下输出:

SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.100:2376
SET DOCKER_CERT_PATH=C:\Users\USER_NAME\.docker\machine\machines\default
SET DOCKER_MACHINE_NAME=default
SET COMPOSE_CONVERT_WINDOWS_PATHS=true
REM Run this command to configure your shell:
REM @FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

复制下面的命令并在cmd上执行:

@FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

然后执行以下命令进行控制:

docker version

2)对于Windows 7 Powershell，以管理员身份运行Powershell .exe，执行以下命令:

docker-machine env --shell=powershell | Invoke-Expression

然后执行以下命令进行控制:

docker version

3)如果重新打开cmd或powershell，应再次重复相关步骤。

2017-06-14 06:54:05

我的一个朋友也有类似的问题，我们尝试了一下，效果很好。

Hyper-V，尽管在“打开或关闭Windows功能”中被列为活动，但实际上并不是活动的。当在PowerShell下运行systeminfo时，这变得很明显，并且看到要求被列出为满足(这不是您期望的Hyper-V实际运行的输出)。步骤:

打开“打开或关闭Windows功能” 如果您不确定如何做到这一点，请参考 https://www.howtogeek.com/250228/what-windows-10s-optional-features-do-and-how-to- [turn-them-on-or-off /] [1] 关闭Hyper-V(取消复选框，确保所有子组件都被标记为关闭) 点击“Ok”-你的机器将重新启动。当你的电脑再次启动时，打开“打开或关闭Windows功能”，然后重新打开Hyper-V。您的机器将重新启动。

现在你可以通过运行docker hello-world image进行测试。

2020-10-14 08:56:46

确保您以“管理员”身份启动Powershell，这也将防止您从docker版本中得到的错误。

到2021年，这些提示可能会过时:

然后尝试启动docker服务:start-service docker 如果失败，删除docker。Pid文件，你可以在CD $env:programfiles\docker;rm docker.pid 最后，您应该将HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Containers\VSmbDisableOplocks更改为0或删除该值。

2016-11-07 12:39:29

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

2022-12-04 10:04:57

在我的例子中，WSL2 Linux-Kernel丢失了，下载，执行并重新启动:

https://learn.microsoft.com/de-de/windows/wsl/wsl2-kernel

解决了问题。

2020-08-11 15:16:02

Docker无法在Windows上启动

推荐文章

最新文章

标签