Kitematic setup error: connect ENOENT //./pipe/docker_engine

[volansky]

On first run setup of kitematic I get this error

error: connect ENOENT //./pipe/docker_engine

Running Docker tool-box on windows 10

[daattali]

I'm on Windows 7 and also got this error just after installing Docker Toolbox

[reloadsweety]

I get same error too , some one help. T-T

[xandermar]

Same here (using Win7)...

[jtumano]

Get the same error too on win7.

[Wangyunxing]

same error on Win7

[daghb]

Same error Win10. Docker 1.12.0 beta 21. Docker Toolbox 1.12.0. Fixed by deinstalling Docker Toolbox and downloading Kitematic only.

[SteeveGL]

Got same issue. I fixed it by this step:

• Double checked Virtualization. It's was disable. Turned it enable in BIOS.
• Relaunched Docker Toolbox
• Got the error again. Clicked on "USE VIRTUALBOX"
• Setup complete successfully.

[xandermar]

True, it works fine when you click "Use Virtualbox" - the error (for me) comes from clicking "Use Docker" or "Retry Setup"

[leegochyi]

Got same issue. I fixed it by this step just try it
win10 pro need stop hyper-v service and reboot pc
and click "Use Virtualbox"
if hava uac worring click yes let it setup Virtualbox

[dbashyal]

Windows 7: I followed above steps to fix this error and 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.

Steps I had to follow:

1. Started virtualbox delete default if there is one.
2. Open Docker Kitematic - gives you above error error: connect ENOENT //./pipe/docker_engine
3. Click "Use Virtualbox", it will add default to virtualbox.
4. Once default is ready try docker-machine restart.
5. Run docker-machine env and then follow instruction to configure.
6. eval $("C:\Program Files\Docker Toolbox\docker-machine.exe" env)
7. All good now. Test by running docker ps -a

or follow - https://github.com/dbashyal/Tips-And-Tricks/blob/master/tips/Docker_Tips_And_Tricks.md

[daattali]

Any word yet from the maintainers of docker? I'm a bit disappointed that such a big error goes by for over a week with so many reports and it seems to be ignored

[xandermar]

For all those who say "...click 'Use Virtualbox'..." - that doesn't solve the problem! The problem is: when you click on USE DOCKER, it throws this error. Please focus on that and not the other button!

[OMarohn]

+1

Windows 8.1

[bbodenmiller]

Also reported at docker/kitematic#1903.

[REVA-AlarmTILT]

+1

Windows 10 - Last update

[FrenchBen]

Kitematic favors the Docker for Windows and Docker for Mac setup. The error shown above is a result of that - You can then use Virtualbox instead of the native setup.
A pending PR in kitematic will allow the setting to be saved, see:
docker/kitematic#1878

[barnabyc]

@FrenchBen - but shouldn't the Native setup work if one installs Kitematic via Docker Toolbox? I think that's the confusion folks in this thread have. Using VirtualBox seems like a different approach instead of an actual resolution - if there's something wrong on my Windows install I'd really prefer fixing it rather than ignoring it.

[xandermar]

I agree with @barnabyc

[daattali]

I agree as well. Or at least make it clear in the documentation how to get it working for windows

[FrenchBen]

@barnabyc I see your point - I'll update the error displayed to be more descriptive.
What I mean by Native is using Docker for Mac or Docker for Windows - The toolbox is bundled with Virtualbox, but Kitematic doesn't have an easy way to determine that.

[bbodenmiller]

If the user is not using an OS that supports Docker for Windows or Mac shouldn't it just try VirtualBox rather than give an error?

[barnabyc]

@FrenchBen - Thank you for clarifying. I am surprised/confused that Docker Toolbox is now not the preferred approach to use for current-gen Windows and Mac platforms. I just re-read their documentation and this sentence jumped out: "Docker Toolbox is an installer for quick setup and launch of a Docker environment on older Mac and Windows systems that do not meet the requirements of the new Docker for Mac and Docker for Windows apps."

This is more of a complaint against the Docker Toolbox installer UX, but it seems odd not to mention this new (to me) development.

I agree with @bbodenmiller that even mentioning an error seems misleading.

As for myself, I'm about to uninstall Docker Toolbox, try the new Docker for Windows installer, and then attempt to reinstall Kitematic, and see what happens.

[FrenchBen]

@barnabyc I'll see if we can add a bit more info as part of the installer of Docker Toolbox.

[1600]

Same here, win 8.1

[nakamorichi]

How to fix this? I don't want to use Virtualbox, but Hyper-V.

[FrenchBen]

@Kitanotori Are you using Docker for Windows? If so, it should work out of the box.

[DrVanScott]

"Docker for Windows" requires Windows 10, right? I am using Windows 7. So i have to live with this error and need to "use virtualbox"? (Which is not a big issue, but i just want to understand this...)

[FrenchBen]

@DrVanScott we're working on cleaning this up and make it more seamless.

[archergod]

Today, I got this error. I have Docker for Windows with Hyper-V on Windows 10. the strange thing is It was working till 2 days ago. 2 days ago I create a docker-machine to try to upload to HUB. but then I have to stop my experiment. After 2 days when I open it up it gives error.

[MikeGitIt]

Why is this closed? I don't see a resolution. I want to use docker but it's been a headache to setup on windows. Could be Windows or it could be PEBKAC. Anyway, I'll just wait until I have time to troubleshoot it and therefore use it.

[FrenchBen]

@MikeGitIt because it's not an actual error, but highlights the fact that Docker for Windows isn't working.
This has been fixed in Kitematic: docker/kitematic#1878

[MikeGitIt]

@FrenchBen I am good now, reverted to my MacBook for a little while and after I had the time and patience, I went back to the Windows laptop, rebooted it, and autoamgically it works. I was/am running the latest version of Kitematic,, so that wasn't my issue AFAICT. I am good now though but I am not sure why other than it is fixed in Kitematic and a reboot somehow allowed it to work as expected.

[hungd02cntt]

"Error: connect ENOENT //./pipe/docker_engine".on win7 it is still error. show me, how to fix??

[nakamorichi]

Installed the latest Docker via https://download.docker.com/win/stable/InstallDocker.msi and now the problems with Kitematic also disappeared. I wonder if the problem lies in Docker Toolbox installer for Windows.

[crzndx]

Still not fixed. "Error: connect ENOENT //./pipe/docker_engine" appearing on Win 8 with latest Docker Toolbox

[nakamorichi]

@crzndx Ignore the toolbox, it doesn't work. Install Docker and Kitematic separately.

[FrenchBen]

@crzndx As mentioned above a new version of kitematic is due - I'm chasing a few community PR before it's all out the door.

[tmizuma]

it seems Hyper-v is not available.
You should make Hyper-v available.
https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install
(only Windows 10 Pro/Enterprise)

[MrBeerBrewer]

Did anyone read +steevegldev 's comment?
I confirm it still works. In my case Virtualization was enabled, but the second part did the trick.

Update: +dbashyal 's solution works too. I was playing around and followed that to get it to work.

[jlark]

+1 windows 10

[lequarti]

I used W10, Docker toolbox + Kitematic

https://forums.docker.com/t/kitematic-wont-launch-unless-i-run-as-administrator/4362/2

[djangofan]

Didn't work for me on Windows10 until I installed Kitematic with the "Virtualbox" button. Wasted hours of time to figure that out. I also started the Docker Quickstart shell before I did that. This twiddling eventually got it working for me.

[nh43de]

Yes, it turns out you need to run as administrator to get past this error. Everything works fine now. Perhaps this is a UX/usability issue.

[zonky2]

Still not fixed. "Error: connect ENOENT //./pipe/docker_engine" appearing on Win7 Pro 64 with latest Docker Toolbox
👎

[sijo0703]

In Windows 7 64 bit you have to use the "Use VirtualBox" option while configuring Kitematic. You cannot install Docker stable version in Windows 7. At least require Windows 10 Pro. Also I cannot find a Kitematic alone version in Kitematic site. So the only option left to configure Kitematic in Windows 7 is to Install Docker Toolbox and choose Use VirtualBox when you get this error!

[diman82]

Get the same error on Win 10 64 bit Enterprise.

[holazt]

This problem has a solution. Please see #1992.

[ghost]

Just got this error today. This is not solved.

[ghost]

@ZetaoYang this is a common misconception. Just because there is a workaround does not mean this is "solved". Whatever the fix is should be done automatically during installation.

[holazt]

@megamindbrian I'm sorry for the wrong words 'solved'.But This solution solved my problem.

[FrenchBen]

@megamindbrian aside from the vbox issue shown in the above mentioned issue, it's been resolved by providing a friendlier error message to the user.

[ghost]

Figured it out finally. Hopefully there is something to learn from this. On the working computer I checked the setting in the client to Expose deamon without TLS. I also added the firewall rule to allow it.

new-netfirewallrule -displayname "docker engine" -direction inbound -action allow -protocol tcp -LocalPort 2375

Where do I file the bug report that the installer for windows isn't adding a rule for the service? Also, This is critical for working on Windows.

Set-NetConnectionProfile -InterfaceAlias "vEthernet (DockerNAT)" -NetworkCategory Private

Is there a fix for either of these user-experience issues?

[jonvuri]

For anyone running across this issue from googling, this solved it for me:

https://stackoverflow.com/questions/34778147/cannot-boot-windows-guest-in-virtualbox-without-kernel-module-error

It's a bit silly this still happens with a vanilla Docker Toolbox install on Windows!

[nakamorichi]

I still recommend avoiding Docker Toolbox and installing the components separately. Install latest Docker from here, and latest Kitematic from here. Depending on your platform, you may need VirtualBox or not. If you have HyperV enabled like me, you SHOULD NOT INSTALL VirtualBox, as it doesn't work when HyperV is enabled.

[jonvuri]

@Kitanotori That's a good suggestion, but considering this is the Docker Toolbox repo and the Toolbox is purportedly offered and supported on Windows, I feel like it should be fixed to work out of the box on it. Not sure why this and other issues are closed when it still doesn't accomplish that.

[VagnerSilva]

I'm using virtualbox so I dont know if it will work for anyone using hyper-v

I added the following parameters in windows environment

COMPOSE_CONVERT_WINDOWS_PATHS=true
DOCKER_CERT_PATH=C:\Users\YOUR_USER_WINDOWS\.docker\machine\machines\default
DOCKER_HOST=tcp://192.168.99.100:2376
DOCKER_MACHINE_NAME=default
DOCKER_TLS_VERIFY=1

Dont need to restart windows just logoff
Start service docker

now cmd, powershell, kitematic, vscode, not show //./pipe/docker_engine
I fixed my problem

[ghost]

I finally got past this by reinstalling "Docker Edge".

…

On Mon, Nov 13, 2017 at 12:29 PM, Vagner Silva ***@***.***> wrote: I'm using virtualbox so I do not know if it will work for anyone using hyper-v I added the following parameters in windows environment [image: virtual] <https://user-images.githubusercontent.com/11982064/32744849-077d4a82-c898-11e7-96f5-23f9d74c1ace.PNG> COMPOSE_CONVERT_WINDOWS_PATHS=true DOCKER_CERT_PATH=C:\Users\YOUR_USER_WINDOWS\.docker\ machine\machines\default DOCKER_HOST=tcp://192.168.99.100:2376 DOCKER_MACHINE_NAME=default DOCKER_TLS_VERIFY=1 now logoff Start service docker now cmd, powershell, kitematic, vscode, not show //./pipe/docker_engine — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#548 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AX5XbmdQgo1WdTFmLZbhpu7kFXlnMSWfks5s2JilgaJpZM4Jezb_> .

-- CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. It is then shared with tech companies, bots, hackers, government agencies, and marketers. The security of this message is none, and it may be shared on Instagram at anytime. If you are OK with this, please respond. There isn't really any security or privacy anywhere. If you disagree you may want to go camping and talk to people face-to-face like in old times.