New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
volansky opened this Issue Aug 8, 2016 · 63 comments

Comments

Projects
None yet
@volansky

volansky commented Aug 8, 2016

On first run setup of kitematic I get this error

error: connect ENOENT //./pipe/docker_engine

Running Docker tool-box on windows 10

@daattali

This comment has been minimized.

daattali commented Aug 10, 2016

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

@reloadsweety

This comment has been minimized.

reloadsweety commented Aug 10, 2016

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

@xandermar

This comment has been minimized.

xandermar commented Aug 10, 2016

Same here (using Win7)...
docker error

@jtumano

This comment has been minimized.

jtumano commented Aug 11, 2016

Get the same error too on win7.

@Wangyunxing

This comment has been minimized.

Wangyunxing commented Aug 12, 2016

same error on Win7

@daghb

This comment has been minimized.

daghb commented Aug 12, 2016

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

@steevegldev

This comment has been minimized.

steevegldev commented Aug 13, 2016

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

This comment has been minimized.

xandermar commented Aug 13, 2016

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

@leegochyi

This comment has been minimized.

leegochyi commented Aug 13, 2016

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

This comment has been minimized.

dbashyal commented Aug 16, 2016

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

This comment has been minimized.

daattali commented Aug 16, 2016

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

This comment has been minimized.

xandermar commented Aug 16, 2016

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

This comment has been minimized.

OMarohn commented Aug 16, 2016

+1

Windows 8.1

@bbodenmiller

This comment has been minimized.

Contributor

bbodenmiller commented Aug 17, 2016

Also reported at docker/kitematic#1903.

@REVA-AlarmTILT

This comment has been minimized.

REVA-AlarmTILT commented Aug 24, 2016

+1

Windows 10 - Last update

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Aug 24, 2016

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

@FrenchBen FrenchBen closed this Aug 24, 2016

@barnabyc

This comment has been minimized.

barnabyc commented Aug 24, 2016

@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

This comment has been minimized.

xandermar commented Aug 24, 2016

I agree with @barnabyc

@daattali

This comment has been minimized.

daattali commented Aug 24, 2016

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

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Aug 25, 2016

@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

This comment has been minimized.

Contributor

bbodenmiller commented Aug 27, 2016

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

This comment has been minimized.

barnabyc commented Aug 27, 2016

@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

This comment has been minimized.

Contributor

FrenchBen commented Aug 30, 2016

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

@1600

This comment has been minimized.

1600 commented Aug 30, 2016

Same here, win 8.1

@Kitanotori

This comment has been minimized.

Kitanotori commented Sep 3, 2016

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

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Sep 5, 2016

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

@DrVanScott

This comment has been minimized.

DrVanScott commented Sep 7, 2016

"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

This comment has been minimized.

Contributor

FrenchBen commented Sep 7, 2016

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

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Sep 9, 2016

To confirm you used Virtualbox with Kitematic first then enabled HyperV?
I could see that failing, as it would have then defaulted to Virtualbox. Perhaps I should add a Try Native when Virtualbox fails

@archergod

This comment has been minimized.

archergod commented Sep 24, 2016

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

This comment has been minimized.

MikeGitIt commented Sep 27, 2016

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

This comment has been minimized.

Contributor

FrenchBen commented Sep 28, 2016

@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

This comment has been minimized.

MikeGitIt commented Sep 29, 2016

@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

This comment has been minimized.

hungd02cntt commented Oct 3, 2016

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

@Kitanotori

This comment has been minimized.

Kitanotori commented Oct 3, 2016

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

This comment has been minimized.

crzndx commented Oct 6, 2016

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

@Kitanotori

This comment has been minimized.

Kitanotori commented Oct 6, 2016

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

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented Oct 6, 2016

@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

This comment has been minimized.

tmizuma commented Oct 10, 2016

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

This comment has been minimized.

MrBeerBrewer commented Oct 20, 2016

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

This comment has been minimized.

jlark commented Nov 2, 2016

+1 windows 10

@lequarti

This comment has been minimized.

lequarti commented Dec 1, 2016

@djangofan

This comment has been minimized.

djangofan commented Dec 9, 2016

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

This comment has been minimized.

nh43de commented Dec 14, 2016

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

This comment has been minimized.

zonky2 commented Jan 6, 2017

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

@sijo0703

This comment has been minimized.

sijo0703 commented Jan 17, 2017

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

This comment has been minimized.

diman82 commented Jan 22, 2017

Get the same error on Win 10 64 bit Enterprise.

@ZetaoYang

This comment has been minimized.

ZetaoYang commented Mar 6, 2017

This problem has a solution. Please see #1992.

@megamindbrian

This comment has been minimized.

megamindbrian commented May 25, 2017

Just got this error today. This is not solved.

@megamindbrian

This comment has been minimized.

megamindbrian commented May 25, 2017

@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.

@ZetaoYang

This comment has been minimized.

ZetaoYang commented May 26, 2017

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

@FrenchBen

This comment has been minimized.

Contributor

FrenchBen commented May 26, 2017

@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.

@megamindbrian

This comment has been minimized.

megamindbrian commented May 26, 2017

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?

@jrajav

This comment has been minimized.

jrajav commented Jun 28, 2017

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!

@Kitanotori

This comment has been minimized.

Kitanotori commented Jun 29, 2017

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.

@jrajav

This comment has been minimized.

jrajav commented Jun 29, 2017

@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

This comment has been minimized.

VagnerSilva commented Nov 13, 2017

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

virtual

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

@megamindbrian

This comment has been minimized.

megamindbrian commented Nov 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment