docker for windows fails on start

john-rene-madsen commented 6 years ago

[x] I have tried with the latest version of my channel (Stable or Edge)
[x] I have uploaded Diagnostics
Diagnostics ID: 4A9B12EB-7B30-4AEE-9A69-B949CDB39FC8/20180801093149

Expected behavior

docker for windows should start the docker environment

Actual behavior

the VM MobyLinuxVM is startet and running in the Hyper-V manager but docker for windows reports "No activity detected on VM, aborting"

Information

Windows Version: OS-navn Microsoft Windows 10 Enterprise Version 10.0.17134 Build 17134
Docker for Windows Version: Version: 18.06.0-ce-win72 (19098) Channel: stable Sha1: 5513f91045dac2b8d51420014ee9176d24791d7d Started on: 2018/08/01 09:28:15.212

Steps to reproduce the behavior

start Docker for Windows on a rebooted machine

Is it possible to reset setting to new MobyLinuxVM image and the import/transfer the docker images from the old VM image ?

ucavalcante commented 6 years ago

im have same problem when i turn off kubernetes docker comes up again in reboot.

rock-it-rob commented 6 years ago

I'm experiencing the same issue and I don't have Kubernetes enabled.

I can watch the Windows Hyper-V manager and see that the MobyLinuxVM is shutting down and then being deleted while Docker is still attempting to start. If I "Restart" docker from the system tray tool it reports that it successfully has restarted but the MobyLinuxVM is still gone.

I had to perform the following step twice to get docker to start correctly:

"Quit Docker" and then relaunch it.

jamieshiz commented 6 years ago

I have "Quit Docker" and relaunched it 3 times in a row and gotten the same error.

No activity detected on VM, aborting 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.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 77 at Docker.Actions.<>cDisplayClass16_0.b0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 61 at Docker.WPF.TaskQueue.<>cDisplayClass19_0.<.ctor>b1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Docker for Windows Version 18.06.0-ce-win72 (19098) Channel: stable 5513f91

Docker Compose Version 1.22.0, build f46880fe

Kubernetes: Off

john-rene-madsen commented 6 years ago

I also have Kubernetes: Off It is a plain Docker for Windows installation just with a lot of images that I will hate to loose. (I only have a backup of the Moby VM image) Is there a way to ssh or the like into the MobyLinuxVM and extract the images ?

Den tor. 2. aug. 2018 kl. 18.42 skrev Jamie Schiesel < notifications@github.com>:

I have "Quit Docker" and relaunched it 3 times in a row and gotten the same error.

No activity detected on VM, aborting 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.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\ github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 77 at Docker.Actions.<>cDisplayClass16_0.b0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 61 at Docker.WPF.TaskQueue.<>cDisplayClass19_0.<.ctor>b1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

Docker for Windows Version 18.06.0-ce-win72 (19098) Channel: stable 5513f91

Docker Compose Version 1.22.0, build f46880fe

Kubernetes: Off

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/2351#issuecomment-409991532, or mute the thread https://github.com/notifications/unsubscribe-auth/APDrYM0WLEw6Z5xQ1bD_u2UKUYBuvTYWks5uMyvcgaJpZM4VqLKC .

ghost commented 6 years ago

facing the same anyone resolved?

robrich commented 6 years ago

I'm having similar issues as discussed on #2214. I'm blocked.

gtardif commented 6 years ago

Hi @john-rene-madsen, @jamieshiz , we have a potential fix for this issue (that we don't reproduce), could you confirm if this build fixes the No activity detected on VM, aborting issue ?

robertgoljat commented 6 years ago

gtardif

could you confirm if this build fixes the No activity detected on VM, aborting issue ?

No, it's not working!

EDIT: The second installation succeeded and it's running (as Linux):

`$ docker version Client: Version: 18.06.1-ce API version: 1.38 Go version: go1.10.3 Git commit: e68fc7a Built: Tue Aug 21 17:21:34 2018 OS/Arch: windows/amd64 Experimental: false

Server: Engine: Version: 18.06.1-ce API version: 1.38 (minimum version 1.12) Go version: go1.10.3 Git commit: e68fc7a Built: Tue Aug 21 17:29:02 2018 OS/Arch: linux/amd64 Experimental: false `

But ifI try to switch to Windows, I get the same error as with previous version:

Here is the list of events in the event viewer:

`Log Name: Application Source: docker Date: 24. 08. 2018 15:12:04 Event ID: 1 Task Category: None Level: Error Keywords: Classic User: N/A Computer: mylaptop2 Description: Error occurred when creating network could not find plugin internal in v1 plugin registry: plugin not found

Log Name: Application Source: docker Date: 24. 08. 2018 15:11:56 Event ID: 1 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: mylaptop2 Description: Unable to locate plugin: internal, retrying in 8s

Log Name: Application Source: docker Date: 24. 08. 2018 15:11:52 Event ID: 1 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: mylaptop2 Description: Unable to locate plugin: internal, retrying in 4s

Log Name: Application Source: docker Date: 24. 08. 2018 15:11:50 Event ID: 1 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: mylaptop2 Description: Unable to locate plugin: internal, retrying in 2s

Log Name: Application Source: docker Date: 24. 08. 2018 15:11:49 Event ID: 1 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: mylaptop2 Description: Unable to locate plugin: internal, retrying in 1s

Log Name: Application Source: docker Date: 24. 08. 2018 15:11:49 Event ID: 2 Task Category: None Level: Information Keywords: Classic User: N/A Computer: mylaptop2 Description: debug: Network Response : { "ActivityId" : "6a8e15c1-8524-4d84-9b26-3f0170fcf115", "CurrentEndpointCount" : 0, "Extensions" : [ { "Id" : "e7c3b2f0-f3c5-48df-af2b-10fed6d72e7a", "IsEnabled" : false, "Name" : "Microsoft Windows Filtering Platform" }, { "Id" : "e9b59cfa-2be1-4b21-828f-b6fbdbddc017", "IsEnabled" : false, "Name" : "Microsoft Azure VFP Switch Extension" }, { "Id" : "ea24cd6c-d17a-4348-9190-09f0d5be83dd", "IsEnabled" : false, "Name" : "Microsoft NDIS Capture" } ], "ID" : "4b819268-17ca-48c6-87bf-c45cf2f51ecd", "LayeredOn" : "3a1f0d60-7754-4255-9b62-50f7b882f6f7", "MacPools" : [ { "EndMacAddress" : "00-15-5D-3D-EF-FF", "StartMacAddress" : "00-15-5D-3D-E0-00" } ], "MaxConcurrentEndpoints" : 0, "Name" : "Intel(R) Dual Band Wireless-N 7260 Virtual Switch", "Policies" : [ ], "Resources" : { "AllocationOrder" : 0, "ID" : "6a8e15c1-8524-4d84-9b26-3f0170fcf115", "PortOperationTime" : 0, "State" : 1, "SwitchOperationTime" : 0, "VfpOperationTime" : 0, "parentId" : "bcd82d61-c6a3-4276-bf27-7f64bc6b85bb" }, "State" : 1, "TotalEndpoints" : 0, "Type" : "Transparent", "Version" : 30064771074 } `

gtardif commented 6 years ago

@robertgoljat Thx to confirm this fixes the linux startup sequence. Can you upload diagnostics so that we can investigate the switch to windows containers (likely unrelated)

robertgoljat commented 6 years ago

Hi Guillaume,

Check the attached diagnostics zip generated by Docker.

Thx to confirm this fixes the linux startup sequence

Actually, I have never had any problems with Linux startup sequence (it always worked). Switching to Windows containers causes problems…

Lep pozdrav / Best regards,

                         Robert Goljat

[smenstorsys_signature_2]

From: Guillaume Tardif notifications@github.com Sent: Friday, August 24, 2018 3:22 PM To: docker/for-win for-win@noreply.github.com Cc: Robert Goljat robert@smenstorsys.com; Mention mention@noreply.github.com Subject: Re: [docker/for-win] docker for windows fails on start (#2351)

@robertgoljathttps://github.com/robertgoljat Thx to confirm this fixes the linux startup sequence. Can you upload diagnostics so that we can investigate the switch to windows containers (likely unrelated)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/docker/for-win/issues/2351#issuecomment-415756785, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOQumPX9G5wt5p6oN3R2lbEWsx9CwL_yks5uT_3fgaJpZM4VqLKC.

john-rene-madsen commented 6 years ago

The latest version fixed my problem

john-rene-madsen commented 6 years ago

PS: I think the issue was mainly a startup timing issue, I have a lot of small containeres and a few big ones in total 80GB. A few times Docker managed to start correct. That allowed my to export the images With the new version it starts correct all the time

syedhassaanahmed commented 5 years ago

Same issue on Stable 18.06.1-ce-win73 (19507) Diagnostic ID: 9E546F03-92E7-4328-A05E-C51EAAD30B9A/20181024022318

leejosh commented 5 years ago

i too am having the same issue. fresh install of server 2016. fresh install of docker 18.06.1-ce

No activity detected on VM, aborting 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.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 77 at Docker.Actions.<>cDisplayClass18_0.b0() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 137 at Docker.WPF.TaskQueue.<>cDisplayClass19_0.<.ctor>b1() in C:\gopath\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59

docker-robott commented 4 years ago

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

docker / for-win