1. 技术文章
  2. docker cannot start on windows

docker cannot start on windows

由 谁说我不能喝 提交于 2019-11-28 16:49:28

Error Code:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.29/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.

Solutions:

1) For Windows 7 Command Window(cmd.exe), open cmd.exe with run as administrator and execute following command:

docker-machine env --shell cmd default

You will receive following output:

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

Copy the command below and execute on cmd:

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

And then execute following command to control:

docker version

2) For Windows 7 Powershell, open powershell.exe with run as administrator and execute following command:

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

And then execute following command to control:

docker version

3) If you reopen cmd or powershell, you should repeat the related steps again.

I know this question was long ago but I found no proper explanation and solution, so hopefully, my answer is useful :)

Assuming you install Docker Toolbox on Windows, both docker and docker-machine commands will be available. Often, people get confused when to use either of these.

The docker commands are used only within a virtual machine to manage images. The docker-machine commands are used on the host to manage the Linux VMs.

So, please use docker-machine commands on your Windows machine. Use docker command inside your VM. To use the docker commands, for example, docker ps, you either can open Docker Quickstart Terminal or run these on your cmd/bash/PowerShell:

docker-machine run default /assuming default is your Linux VM/

docker-machine ssh default

This will start boot2docker and you will see the docker icon on the command line. Then you can use docker commands.

Good luck :)

Jdoe

You can run "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon and point Docker CLI to either Linux or Windows containers. This worked for me.

For me the issue was virtualization was not enabled.

On windows 10: Go to task manager -> Performance -> CPU and you should see as section as "Virtualization : Enabled"

If you do not see this option, it means that virtualization has not been enabled.

Another interesting thing to note is you must have Hyper V enabled. However as I was using parallels desktop, I had to enabled to "Nested Virtualization" for Hyper V to be "truly enabled". So if your windows is a VM, check out the settings for Parallels (or whatever you're using) that nested virtualization is enabled.

I had the same issue lately. Problem was Security Software(Trendmicro) was blocking docker to create Hyperv network interface. You should also check firewall, AV software not blocking installation or configuration.

Prabhat Maurya

If you have installed docker on Windows 10 Pro with Hyper-V enabled and you are still not able to run Docker on Windows 10, then, as the error suggests, your docker daemon is not started.

The following steps helped me to start docker successfully:

  1. Use command on cmd(Admin mode)

    docker-machine restart default

  2. Then you'll get a message something like:

    open C:\User\\{User_name}\\.docker\machine\machines\default\config.json:
    The system cannot find the file specified.

  3. Go to the docker icon which will be on your windows tray (bottom right corner of the desktop)

  4. Right click on the docker icon > Settings > Reset > Restart Docker

    It will take few moments

  5. Then you'll see the following message:

    Docker is running with the green indicator

Note: If you already had Docker containers running on your system, then don't follow these steps. You may lose the existing containers.

if you are in windows try this

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

for testing try 

docker run hello-world

For win10 I had the same issue:

error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/images/load?quiet=0: 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.

The docker service appeared to work. Restarting did not help. Running the binary from the installation directory as administrator helped.

In my case:

run as administrator -> C:\Program Files\Docker\Docker\Docker for Windows.exe
MayankGaur

Try resolving the issue with either of the following options:

Option A

Start-Service "Hyper-V Virtual Machine Management"
Start-Service "Hyper-V Host Compute Service"

or

Option B

  1. Open "Window Security"

  2. Open "App & Browser control"

  3. Click "Exploit protection settings" at the bottom

  4. Switch to "Program settings" tab

  5. Locate "C:\WINDOWS\System32\vmcompute.exe" in the list and expand it

  6. Click "Edit"

  7. Scroll down to "Code flow guard (CFG)" and uncheck "Override system settings"

  8. Start vmcompute from powershell "net start vmcompute"

  9. Then restart your system

I am using Windows 7 with Docker Toolbox and to fix it just open Docker Quickstart Terminal.

$ docker version Client: Version: 17.05.0-ce API version: 1.29 Go version: go1.7.5 Git commit: 89658be Built: Fri May 5 15:36:11 2017 OS/Arch: windows/amd64

Server: Version: 17.05.0-ce API version: 1.29 (minimum version 1.12) Go version: go1.7.5 Git commit: 89658be Built: Thu May 4 21:43:09 2017 OS/Arch: linux/amd64 Experimental: false

I run in to the same problem. I solved this by enabling hyper-v.

  1. Enable virtualization in BIOS
  2. Install hyper-v

Try running the following from an elevated command prompt:

SET DOCKER_CERT_PATH=C:\Users\[YourName]\.docker\machine\machines\default
SET DOCKER_HOST=tcp://[yourDockerDeamonIp]:2376
SET DOCKER_MACHINE_NAME=default
SET DOCKER_TLS_VERIFY=1
SET DOCKER_TOOLBOX_INSTALL_PATH=C:\Program Files\Docker Toolbox

You might also find that even without setting those env variables, running commands from the docker quick start terminal works no problem.

I was getting same errors after an install on Windows 10. And I tried restarting but it did not work, so I did the following (do not recommend if you have been working in docker for awhile, this was on a fresh install):

1) Find the whale in your system tray, and right click

2) Go to settings > Reset

3) Reset to factory defaults

I was then able to follow the starting docker tutorial on the website with Windows 10, and now it works like a charm.

For me the error was resolved by stopping a virtual Ubuntu instance that'd been running in Hyper-V:

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.

Once Ubuntu instance had been stopped, and Docker Desktop had been restarted, my usual docker commands ran just fine.

PS: I had the idea to try this because of an Error Log that Docker Desktop had helpfully compiled and offered to send to Docker Hub as user feedback... the log appeared to indicate that my machine was short on RAM, and Docker was failing for this very simple reason. Killing the Ubuntu instance solved that.

1st start Powershell "as Administrator" that will also prevent the error you got from docker version.

The try to start the docker service: start-service docker If that fails delete the docker.pid file you will find with cd $env:programfiles\docker; rm docker.pid
Finally you should change HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Containers\VSmbDisableOplocks to 0 or delete the value.

You can start Kitematic when you get this error. It will display a button to reset the VM and will fix the issue.

I had the same error on Windows. Turns out I was missing the Container feature.

Install-WindowsFeature Containers

Restart server

When up and running ensure the Docker service is running

I am using window 10 and i performed below steps to resolve this issue.

  1. check Virtualization is enabled from taskmanager-->performance
  2. Restarted the docker service
  3. Install the latest docker build and restarted the machine.
  4. Make sure the docker service is running.

Above steps helped me to resolve the issue.

This is the final solution.. its works for me...!!

1) Find the whale in your system tray, and right click

2) Go to settings > Reset

3) Reset to factory defaults

标签
Docker
docker-for-windows
易学教程内所有资源均来自网络或用户发布的内容，如有违反法律规定的内容欢迎反馈！
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!