在 Windows 上执行泊客版本
命令将返回以下结果:
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>
您可以运行< code > " C:\ Program Files \ Docker \ Docker \ DockerCli . exe "-switch daemon 并将Docker CLI指向Linux或Windows容器。这对我很有效。
我也有同样的问题。
启动Docker Desktop后,确保左下角的docker守护进程状态为绿色,并在您将鼠标悬停在它上面时显示RUNING。
该错误与该部分有关:
在Windows上的默认守护程序配置中,必须运行提升的docker客户端才能连接
>
首先,确认Docker Desktop应用程序正在运行。如果没有,启动它:它将运行docker守护进程(只需等待几分钟)。
然后,如果错误仍然存在,您可以尝试切换Docker守护程序类型,如下所述:
带强力外壳:
或者,使用cmd:
以管理员身份打开 cmd
- 启动命令:
“C:\程序文件\Docker\Docker\Dockercli.exe” -SwitchDaemon
问题内容: 我是Docker的新手。安装Docker Toolbox(OS:Windows 10)之后,我运行Docker Quickstart Terminal,并在控制台中看到以下内容: 我做错什么了?系统和安装步骤的所有检查均从此处进行。 非常感谢您的帮助! 问题答案: 在Windows 10计算机上安装Docker Toolbox时遇到了相同的错误。 解: 安装Docker Communi
java 15.0.2 2021-01-19 java(TM)SE运行时环境(构建15.0.2 7-27)java热点(TM)64位服务器虚拟机(构建15.0.2 7-27,混合模式,共享)sonarqube-8.7.0.41497
我是一个新来的靠窗工人。我已经安装了Docker工具箱版本,因为我的笔记本电脑无法运行hyper-v。安装Docker Toolbox(操作系统为Windows 10 Home)后,我运行Docker Quickstart Terminal,在控制台中看到: 正在运行预创建检查...创建前检查错误:“此计算机未启用 VT-X/AMD-v。在BIOS中启用它是强制性的“在步骤”检查计算机默认值是否存
Invoke-Neo4j:无法确定E:\neo4j处的安装版本 在行:1字符:175 尝试{unblock-file-path'e:\neo4j\bin\neo4j-management*.*'-erroraction'silentlycontinue'>catch<>;import-module null
我已经在Windows Server 2019上安装了Minikube与Docker一起使用。但是,当我尝试从开始时,它显示以下错误: 启动超虚拟机失败。运行“minikube delete”可能会修复它:加载现有主机时出错。 Hyper-V\Start-VM minikube 无法修复此问题。 当我以
Jenkins构建在Windows从机上运行会在构建开始时抛出以下错误: 我试过的:1。指定TF的完整路径。执行2。指定TF的路径。路径变量3中的exe。设置路径=。在构建过程初始阶段4。设置类路径=。在构建过程初始阶段5。设置类路径=。作为从机上的环境变量。 TF。exe是在Jenkins Slave service user下的任何目录下解析的,因此它不是TF的路径问题。exe文件 感谢您对使