Docker commands fails (in Windows)

Question

I am trying to use Docker on a windows machine and is hit with every possible issue it seems. My latest one is this: My machine is running but I can't seem to interact with it using the docker commands. If I run a very standard command like:

docker ps

I get an error message like this:

An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v
1.23/containers/json: open //./pipe/docker_engine: The system cannot find the file specified.

So apparently some path is all messed up. Do anyone know which path this is and how to fix this?

In tray Docker is running, however in Docker->Settings is status: unable to start. Click to Restart Docker fixes error — Сергей Петроченко, Dec 25 '16 at 09:22

score 60 · Answer 1 · edited Sep 12 '21 at 14:04

60

Edit (2021) - This answer is for the old Docker Toolbox, not Docker Desktop.

When running docker ps and receiving:

An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json: open //./pipe/docker_engine: The system cannot find the file specified.

The following environment properties need to be set:

 set DOCKER_CERT_PATH=%USERPROFILE%\.docker\machine\machines\default
 set DOCKER_HOST=tcp://192.168.99.100:2376
 set DOCKER_MACHINE_NAME=default
 set DOCKER_TLS_VERIFY=1

This is assuming the %USERPROFILE%\.docker\machine\machines\default is default path where the cert.pem, key.pem, ca-key.pem, and ca.pem docker files are; the virtual machine name's (created by docker-machine create) is default and Virtual Box DHCP Server's lower bound (found under VirtualBox->File->Preferences->Network->Host-only Networks->hover mouse on VirtualBox Host-Only Ethernet Adapter) is 192.168.99.100 and no other VM is running in VirtualBox.

edited Sep 12 '21 at 14:04

OneCricketeer

179,855
19
132
245

answered Sep 06 '16 at 13:52

jan.supol

2,636
1
26
31

thanks, that works for me, but i have to run these commands every time i open my command prompt. Is there any way i can set the values permanently. – HyperioN Sep 07 '16 at 11:58
2

Does [How to set the path and environment variables in Windows](http://www.computerhope.com/issues/ch000549.htm) help? – jan.supol Sep 07 '16 at 12:14
1

After setting the parameters, I am getting following message: An error occurred trying to connect: Post https://xxx.xx.xx:2376/v1.24/imag es/create?fromImage=hello-world&tag=latest: dial tcp xx.xxx.xx.xx:2376: connec tex: A connection attempt failed because the connected party did not properly re spond after a period of time, or established connection failed because connected host has failed to respond. Where xxx is the lower bound. – TechTurtle Dec 19 '16 at 20:27
4

If you execute `docker-machine env --shell cmd` it will show these instructions, as well as a copy-paste-able shorthand to run them – nathanleclaire Dec 20 '16 at 01:20
@TechTurtle you need to set your proxy – HankCa Dec 07 '17 at 05:18
Wow I already like Vagrant better. None of that is required for Vagrant. And none of that is even mentioned in the documentation! https://docs.docker.com/get-started/#prepare-your-docker-environment – Chloe Apr 27 '18 at 18:44
1

`>dir %USERPROFILE%\.docker\machine\machines\default The system cannot find the path specified.` – Chloe Apr 27 '18 at 19:20
@jan.supol, does this apply to Docker for Windows (as well as Docker Toolbox). Does the installation process not set these variables? I have asked a similar question here and would be grateful for an answer from you: https://stackoverflow.com/questions/51465944/cannot-switch-from-linux-container-to-windows-container +1. – w0051977 Jul 23 '18 at 10:20

score 19 · Answer 2 · edited Jun 20 '20 at 09:12

19

Same issue here on Win 7. Solution:

In the Docker Quickstart window, at the $ prompt run the below line:

your_user@your_machine MINGW64 ~

$ eval $("C:\Program Files\Docker Toolbox\docker-machine.exe" env default)

Then, you'll be able to run "docker run hello-world".

edited Jun 20 '20 at 09:12

Community

1
1

answered Oct 11 '16 at 22:34

r590

689
1
10
15

score 17 · Answer 3 · answered Jun 01 '16 at 19:51

17

I run into this problem when using docker-machine and I haven't run the docker-machine env command after rebooting. I'm not sure how to do this in cmd.exe, but if you're using powershell try issuing this command:

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

answered Jun 01 '16 at 19:51

aurath

1,347
3
13
19

1

This worked for me, do we know why it solves this problem? I used to not have but I think an MS update broke Docker. I'd like a permament solution. – hamsterofdark Aug 30 '16 at 15:28
1

@hamsterofdark `docker-machine env` displays the command to configure your shell to use the Docker client, whatever the shell is (it tries to detect the shell automatically if you don't include the `shell` parameter). Aurath's answer immediately invokes the returned command. – Thriggle Oct 26 '16 at 18:16
6

`Error: No machine name(s) specified and no "default" machine exists` – Chloe Apr 27 '18 at 19:24

score 10 · Answer 4 · answered Aug 17 '16 at 11:19

10

Make sure Hyper-V is up and running:

open elevated command prompt
type bcdedit /set hypervisorlaunchtype auto
reboot
run "Docker for Windows"

answered Aug 17 '16 at 11:19

Dunken

8,481
7
54
87

5

To clear up some confusion: installation of docker on Windows has two versions: "Docker Toolbox" (Older version, uses VirtualBox) and "Docker for Windows" (Newer version, uses native Hyper-V). If you're running Docker Toolbox, see other answers. If you're running Docker for Windows, use this answer. – pretzels1337 Jun 16 '17 at 15:31

score 6 · Answer 5 · answered May 21 '17 at 12:17

I had to deal with the same issue on Windows.

To solve it:

Create a docker machine (only if you have not got one)
```
docker-machine create  default
```
Get the ENV vars which the docker client needs in order to connect to the docker machine (server) [This you will need to do every time or set in your ENV vars]
```
docker-machine.exe env default
```
You can either install them manually or run one of the following depending on your shell environment (cmd, bash, power-shell)
```
docker-machine env --shell=cmd # you need to run it manually
docker-machine env --shell=bash > env-var-commands-tmp && . env-var-commands-tmp && rm env-var-commands-tmp
docker-machine env --shell=powershell | Invoke-Expression
```

in my case i had ran : docker-machine create default --virtualbox-no-vtx-check — Tiago Medici, Nov 18 '19 at 12:56

score 6 · Answer 6 · answered Jun 01 '17 at 03:26

6

Open cmd with admin rights.
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.102:2376

SET DOCKER_CERT_PATH=C:\Users\DBashyal.docker\machine\machines\default

SET DOCKER_MACHINE_NAME=default

REM Run this command to configure your shell:

REM @FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i
Copy the highlighted line and execute on cmd

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

docker ps

answered Jun 01 '17 at 03:26

Shivendra

159
1
7

default is undefined. How to define it first – Muhaimin Aug 17 '17 at 03:50
`Error: No machine name(s) specified and no "default" machine exists` – Chloe Apr 27 '18 at 19:10

score 5 · Answer 7 · answered Jan 24 '17 at 04:36

5

I created a new machine using the below command

docker-machine create --driver=virtualbox vbox-test

Then executed the command

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

Got it Working...

answered Jan 24 '17 at 04:36

Sunil

553
1
12
30

score 3 · Answer 8 · answered Oct 17 '16 at 15:54

I had a look at all the above answers and none of them worked. Then I found out that the command has to be run on a linux command line like bash. so try:

Type the command into the Docker bash terminal VM that comes with the docker toolbox as opposed to the windows cmd

If you have already made sure that your docker has been started

score 3 · Answer 9 · answered Feb 05 '17 at 21:25

3

As pointed in other answers you need to set a few environment variables.

The easiest way to do it is:

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

This will run docker-machine env --shell cmd and add those environmental variables.

If you want these variables to be persistent defined them in windows (tutorial).

answered Feb 05 '17 at 21:25

NBajanca

3,544
3
26
53

`Error: No machine name(s) specified and no "default" machine exists` – Chloe Apr 27 '18 at 19:11

score 2 · Answer 10 · answered Nov 09 '17 at 20:10

2

Right click the Docker icon in the tray a select "Switch to Windows containers...". You may be prompted to enable the Containers feature. Do so and reboot, again.

answered Nov 09 '17 at 20:10

abmpu

21
1

Bablu Ahmed · Answer 11 · 2019-05-25T14:16:00.733

To start default host in windows I know three ways given below you can use one of them.

Starting or restarting already created a default machine by the Docker:
```
docker-machine start default
docker-machine restart default
```
Now check docker-machine env

The following environment properties need to be set:

set DOCKER_CERT_PATH=%USERPROFILE%\.docker\machine\machines\default
set DOCKER_HOST=tcp://192.168.99.100:2376
set DOCKER_MACHINE_NAME=default
set DOCKER_TLS_VERIFY=1

To create a new machine using the following command:

Windows 10/HyperV:

docker-machine create --driver hyperv default
docker-machine create -d hyperv default

Mac, Linux, windows 7 & 8:

docker-machine create --driver virtualbox default
docker-machine create -d virtualbox default

default machine is already present, so you would want to give some other name — Derrick, May 03 '20 at 15:09

score 1 · Answer 12 · answered Nov 21 '17 at 14:02

I had similar issue when I installed Docker CE for Windows Version 17.11.0-ce-rc4-win39 (14244) Channel: edge e557194 on Windows 10.

In Command/cmd windows, when I tried to run commands docker ps, docker version, docker info, the I got error like “error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.34/version” every time.

To resolved this issue,

I made “Hyper-V” off (Unchecked) from “Turn Windows feature on or off”, which required the OS to be restarted.
And after first restart, I made “Hyper-V” On (Checked), which again required the OS to be restarted.

After second restart, above docker commands started working and giving proper output.

So, turning Hyper-V off and then on resolved this issue for me.

Diya Li · Answer 13 · 2019-10-09T03:16:38.533

I got the solution from this issue. It not just like Nikesh's answer said SwitchDaemon could fix it directly. I think you should run this command twice to switch your daemon to your previous daemon.

cd "C:\Program Files\Docker\Docker"
./DockerCli.exe -SwitchDaemon
# then check the docker OS/Arch
docker version
# You may see the different OS/Arch 
./DockerCli.exe -SwitchDaemon
# then you got your images and containers back

This command is just switch your daemon from your defualt daemon to another daemon(depends on what you set). When you switch to another daemon, the images and containers on the former daemon will disappear(but not deleted).

I ran `./DockerCli.exe -SwitchDaemon` just once and everything was fixed. Thanks. — UserControl, Oct 08 '19 at 07:45

score 0 · Answer 14 · answered Oct 14 '16 at 22:24

I have had this issue on a Windows 2016 machine. Happened because the docker service wasn't started. In my case the docker service as failing with the following error

fatal: Error starting daemon: pid file found, ensure docker is not running or delete C:\ProgramData\docker.pid

Deleting the C:\ProgramData\docker.pid file did the trick.

score 0 · Answer 15 · answered Apr 02 '17 at 18:33

0

below resolved. i copied answer from another forum

I had this problem after update. After re-installing VB I switched on "VirtualBox NDIS6 Bridged Networking Driver" in properties network connection.

It property switched off default in my case.

answered Apr 02 '17 at 18:33

Roninio

1,761
1
17
24

score 0 · Answer 16 · answered Jun 15 '17 at 22:55

Windows 10 Professional For me the Docker service was running but Docker still needed to be 'started'. That is, I had the setting 'Start Docker when you log in' unchecked in the Docker tray icon.

Prior to finding this out I had gone to the program folder Docker and clicked 'Docker for Windows'. After a short time the message 'Docker is running' was displayed.

score 0 · Answer 17 · edited Sep 27 '17 at 08:08

0

For me, this error was resolved after I removed daemon.json file in "%programdata%\docker\config"

The content in my daemon.json is the following:

{
  "hosts": ["tcp://0.0.0.0:2375"]
}

I created this manually as part of some testing. But after I restarted the server, I started to get the error in this question.

edited Sep 27 '17 at 08:08

complex857

20,425
6
51
54

answered Sep 27 '17 at 07:58

Lijo George

11

@Chloe the file isn't created by default, so your system couldn't find it. This is a good answer and a potential solution for people facing this issue – ddrake12 Jul 24 '18 at 21:10
`>dir "%programdata%\docker\config"` `The system cannot find the file specified.` – Chloe Jul 25 '18 at 04:35

Nditah · Answer 18 · 2017-10-10T14:42:48.200

The error is really troubling. I hope Docker Developers do something about. It took a lot of try and error to get around. Thanks to Stackoverflow and other blogs. In my case, I am using Windows 10 Pro. I settled with DockerToolbox.exe after several failed attempts with Docker for Windows Installer.exe. Then I encountered An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v . The followed these steps and the problem got solved. First, I went to Control Panel -> Turn Windows Features On or Off and unchecked Hyper-V
Next, Open PowerShell as Admin:

docker-machine env --shell=powershell | Invoke-Expression
type bcdedit /set hypervisorlaunchtype auto

Restarted my System. Then I launched "Docker Quickstart Terminal", then I entered this on the shell window.

run "Docker for Windows"
docker run hello-world

I it went well. Then I open Command Prompt

docker run hello-world

It gave the error: Then I entered

set DOCKER_CERT_PATH=%USERPROFILE%\.docker\machine\machines\default
set DOCKER_HOST=tcp://192.168.99.100:2376
set DOCKER_MACHINE_NAME=default
set DOCKER_TLS_VERIFY=1

Most of the suggestions above too are helpful.

score 0 · Answer 19 · answered Feb 12 '18 at 19:23

0

I saw this error message after a weekend. My setup was fine before that. My config and connections looked correct. $docker-machine restart default fixed it for me on Windows 7

answered Feb 12 '18 at 19:23

dirtyqwerty

185
2
16

`Docker machine "default" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.` – Chloe Apr 27 '18 at 19:17

score 0 · Answer 20 · answered Jun 12 '18 at 13:21

0

I was getting this error, while running the command docker-compose up. The problem for me was, the docker service was not running. So I had to run services.msc and start the docker service.

answered Jun 12 '18 at 13:21

Sibeesh Venu

18,755
12
103
140

score 0 · Answer 21 · answered Sep 05 '18 at 09:50

0

I solved this error by run the {DOCKER_TOOLBOX_INSTALL_PATH}start.sh in bash.

answered Sep 05 '18 at 09:50

kinglao

151
9

score 0 · Answer 22 · answered Jan 30 '19 at 08:04

0

In my case, all above solutions did not resolve. Instead zilurrane response helped.

    cd "C:\Program Files\Docker\Docker"
    ./DockerCli.exe -SwitchDaemon

answered Jan 30 '19 at 08:04

Nikesh Devaki

2,091
2
16
24

score 0 · Answer 23 · answered Mar 15 '19 at 06:52

0

Switch to Windows Containers
docker info
docker ps
Switch back to Linux containers
docker info
Viola!

The windows switch likely runs the missing configurations that Linux also needs.

answered Mar 15 '19 at 06:52

rism

11,932
16
76
116

score 0 · Answer 24 · answered Jun 25 '19 at 04:53

I was having similar issue. For me I hadn't logged in to docker from the status bar. What I did was to login to docker from status bar. Once I logged in I was able to run all the commands properly. Try logging in using your docker id and password maybe that will resolve your issue.

score -1 · Answer 25 · answered Jul 28 '17 at 15:34

I had the same issue on my Windows 10. Find below what I did to solve it:

After installing Docker, Just restart your PC, run docker application (It may require enabling Hyper-V), then open command line and type: docker run hello-world

Everything works fine :)

BehrouzMoslem · Answer 26 · 2022-12-08T05:27:31.383

-1

I had this problem. I searched a lot. I checked many things. But in the end, the solution that solved my problem was the following solution.

System Environment:

Windows 10 Professional
Windows engine in Docker
Docker version 20.10.21

Solution

disabled IP6 And Restarted the service and application

edited Dec 08 '22 at 05:27

answered Dec 07 '22 at 15:48

BehrouzMoslem

9,053
3
27
34

Docker commands fails (in Windows)

26 Answers26

Linked