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
Docker for Windows Failed to start - error during connect -- //./pipe/docker_engine: The system cannot find the file specified. #2028
Comments
@cmosguy |
@cmosguy there seem to be two issues in your logs: First, the LinuxVM boots really slow:
Typically a normal system would get to this stage in like 2-5 seconds. On your system it takes 60s. See also #1995 Then it boots but there is a go backtrace in the logs (see below). The backtrace looks very similar to moby/moby#27423 which was cause by Lavasoft web companion. Are you running it (or other AV software)? Here is the backtrace
|
Hello @jasonbivins and @rn Thanks for your help. I did the following with the combination of your advice:
In summary, I do not know for sure what the difference between windows vs non-windows containers yet when i am running in this mode or what the drawbacks are but it seems to get me going for now. But this is not what I want because I get this:
This is not a good solution, but it is only meant to help with debugging. Also, I do not understand what was updated by my IT on my system, that created a change to break the docker application. I think there is something going on with the go Thanks! |
Hmm, this is the first time I'm seeing this error. What happens is that there is a process which opens a socket and then connect to it. That works fine, but the call to I don't think it is related to permission as that ought to return "Permission denied" type errors. We have quite a few users on the same Windows build as you and this is the first time I see this type of crash. So for now I'm inclined to think it is something local to your system. I think there is an experimental feature, called LCOW (Linux Containers on Windows) which is enabled when you switch to Window Containers. When in Windows container mode, could you try:
and see if this works? |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Docker for windows should just load and start.
Actual behavior
I get the infamous error:
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: