Docker fails to start with Linux containers support on Windows 10 Pro 1709 #1224

rvprasad · 2017-10-19T16:37:43Z

Expected behavior

Upon starting Docker on Windows 10 Pro (at least prior to Version 1709), Docker starts with no issues -- displays message "Docker is up and running!"

Actual behavior

Upon starting Docker on Windows 10 Pro Version 1709, Docker displays a window with following error message.

Unable to create: The running command stopped because the preference variable ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'MYCOMPUTERNAME' because the object was not found. The object might have been deleted, or you might not have permission to perform the task. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.
at New-MobyLinuxVM, : line 192
at , : line 385
at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\HyperV.cs:line 177
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings, String daemonOptions) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 123
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Issuing docker version command from the command line results in the following error message

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

Information

Diagnostic ID: 17A5BBF0-D955-4DB7-A538-CEF004DD5BA1/2017-10-19_11-19-25
Windows 10 Pro -- Version 1709, Build 16299.19
Docker -- Version 17.09.0-ce-win34 (13622), Channel: edge, 9171a03
Same is true with latest version of Docker available from stable channel
Only happens with Linux containers

Steps to reproduce the behavior

Start Windows 10 Pro
Start Docker -- Make sure Docker is configured to support "Linux containers"

The text was updated successfully, but these errors were encountered:

MosterAndMonk · 2017-10-20T12:07:10Z

About the second steps
how can I do that?
'''Start Docker -- Make sure Docker is configured to support "Linux containers"'''

rvprasad · 2017-10-20T17:44:52Z

Once you start on "Docker for Windows", right click on the the docker icon in the system tray. If you see "Switch to Windows Containers" in the popup menu, then Docker is supporting in Linux containers. If you instead see "Switch to Linux Containers", then Docker is supporting Windows containers and you will need to click on this menu option to switch over to the support for Linux containers.

MosterAndMonk · 2017-10-21T00:56:29Z

Thank you so much for explaining in detail! But seems that I suffered a different problem.
Maybe I should open a new issue to solve the problem, but now I have no ideas.

The docker version command error message is same as yours.
When I clicked on "Switch to Linux Containers", my error info is
"Binary stream "0" does not contain valid BinaryHeader. This may be due to invalid flow, or due to changes in the object version between serialization and serialization. In Docker.Core.Pipe.NamedPipeClient.Send (String action, Object[] parameters) position C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs: line 36 At Docker.Actions.<>c__DisplayClass25_0.b__0 () position C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs: line 285 At Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1 () position C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs: line 59 "

rvprasad · 2017-10-21T01:21:32Z

I'd say so. Please make sure you document all the steps that you took and all the errors encountered. I think this will help folks figure out if the issues are related.

randomvariable · 2017-10-21T10:39:09Z

No joy for me on version 1709, build 16299.19, but for different reasons:

Client:
 Version:      17.09.0-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:40:09 2017
 OS/Arch:      windows/amd64

Server:
 Version:      master-dockerproject-2017-10-20
 API version:  1.34 (minimum version 1.24)
 Go version:   go1.8.4
 Git commit:   ab0eb8f
 Built:        Fri Oct 20 23:50:34 2017
 OS/Arch:      windows/amd64
 Experimental: true

when instantiated with the preview docs, i.e.
Shell 1:

$progressPreference = 'silentlyContinue'
mkdir "$Env:ProgramFiles\Linux Containers”

Invoke-WebRequest -UseBasicParsing -OutFile linuxkit.zip https://github.com/friism/linuxkit/releases/download/preview-1/linuxkit.zip

Expand-Archive linuxkit.zip -DestinationPath "$Env:ProgramFiles\Linux Containers\."
rm linuxkit.zip
Invoke-WebRequest -UseBasicParsing -OutFile dockerd.exe https://master.dockerproject.org/windows/x86_64/dockerd.exe

Shell 2:

docker -H "npipe:////./pipe//docker_lcow" run -ti busybox sh

fails with

Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: no matching manifest for windows/amd64 in the manifest list entries.

docker.log

rvprasad · 2017-10-26T17:32:38Z

This failure does not occur when Docker 17.10.0-ce-win36 (13788) from edge channel is used with "Linux containers for Windows" support. #1221 (comment)

docker-robott · 2018-03-27T10:10:16Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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.
/lifecycle stale

john-thomas-dotcms · 2018-06-08T03:57:51Z

I'm getting the exact same error on 18.3.1-ce when I try to use Linux containers. The error comes up on a cold start, and any time I switch from Windows containers to Linux containers.

john-thomas-dotcms · 2018-06-08T04:09:13Z

I tried with edge 18.05.0-ce and I get the same error. Here is the full text of the error with the edge install:

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'SUREVICTORY10' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.
at New-Switch, <No file>: line 117
at <ScriptBlock>, <No file>: line 394
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
   at Docker.Actions.<>c__DisplayClass24_0.<SwitchDaemon>b__0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 272
   at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

john-thomas-dotcms · 2018-06-08T15:07:38Z

@rvprasad I'm seeing this issue with 18.03.1 and 18.05.0, on Win 10 Pro with the latest Windows Updates. Will this issue get re-looked at, or should I open another issue or ?????

rvprasad · 2018-06-08T15:58:12Z

Since this issue has been closed, I suggest opening a new issue. For me, Linux containers were failing on the latest version of Docker for Windows. So, if you create an issue and I will chime in with my observations.

nlata15 · 2018-06-23T20:13:35Z

Is the issue resolved? Do we have another thread to followup on this?

rvprasad · 2018-06-24T02:43:32Z

I suggest you could create a new issue and/or follow #1221.

josh-axy · 2019-09-21T10:46:56Z

Same with me.

john-thomas-dotcms · 2019-09-23T14:10:38Z

I had this issue for a while, but the issue went away after I did a major Windows Update (which incidentally wiped out most of my custom registry settings) and then installed v2.0.5.0.

Whether the fix happened because of the registry wiping Windows so kindly did for me, or the new version of Docker, I don't know. But if you haven't already, I'd suggest a complete uninstall of both Docker and Hyper-V (including clearing out any left-over registry entries for both), and then re-installing Docker v2.0.5.0 or later.

docker-robott · 2020-06-24T03:14:37Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked

rvprasad mentioned this issue Oct 19, 2017

Docker for Windows (and Hyper-V) not working after update to Windows 10 1709 #1221

Closed

jasonbivins added area/hyper-v area/windows 10 status/triage labels Oct 19, 2017

andydempster mentioned this issue Oct 20, 2017

Docker fails to do a cold start #1075

Closed

guillaumerose added the lifecycle/stale label Mar 27, 2018

docker-robott closed this as completed May 14, 2018

docker locked and limited conversation to collaborators Jun 24, 2020

docker-robott added the lifecycle/locked label Jun 24, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker fails to start with Linux containers support on Windows 10 Pro 1709 #1224

Docker fails to start with Linux containers support on Windows 10 Pro 1709 #1224

rvprasad commented Oct 19, 2017 •

edited

MosterAndMonk commented Oct 20, 2017 •

edited

rvprasad commented Oct 20, 2017

MosterAndMonk commented Oct 21, 2017 •

edited

rvprasad commented Oct 21, 2017

randomvariable commented Oct 21, 2017 •

edited

rvprasad commented Oct 26, 2017 •

edited

docker-robott commented Mar 27, 2018

john-thomas-dotcms commented Jun 8, 2018

john-thomas-dotcms commented Jun 8, 2018 •

edited

john-thomas-dotcms commented Jun 8, 2018

rvprasad commented Jun 8, 2018

nlata15 commented Jun 23, 2018

rvprasad commented Jun 24, 2018

josh-axy commented Sep 21, 2019

john-thomas-dotcms commented Sep 23, 2019

docker-robott commented Jun 24, 2020

Docker fails to start with Linux containers support on Windows 10 Pro 1709 #1224

Docker fails to start with Linux containers support on Windows 10 Pro 1709 #1224

Comments

rvprasad commented Oct 19, 2017 • edited

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

MosterAndMonk commented Oct 20, 2017 • edited

rvprasad commented Oct 20, 2017

MosterAndMonk commented Oct 21, 2017 • edited

rvprasad commented Oct 21, 2017

randomvariable commented Oct 21, 2017 • edited

rvprasad commented Oct 26, 2017 • edited

docker-robott commented Mar 27, 2018

john-thomas-dotcms commented Jun 8, 2018

john-thomas-dotcms commented Jun 8, 2018 • edited

john-thomas-dotcms commented Jun 8, 2018

rvprasad commented Jun 8, 2018

nlata15 commented Jun 23, 2018

rvprasad commented Jun 24, 2018

josh-axy commented Sep 21, 2019

john-thomas-dotcms commented Sep 23, 2019

docker-robott commented Jun 24, 2020

rvprasad commented Oct 19, 2017 •

edited

MosterAndMonk commented Oct 20, 2017 •

edited

MosterAndMonk commented Oct 21, 2017 •

edited

randomvariable commented Oct 21, 2017 •

edited

rvprasad commented Oct 26, 2017 •

edited

john-thomas-dotcms commented Jun 8, 2018 •

edited