Docker not initializing after update

Same problem here on Windows 10 without Insider program. Docker is always initializing.
I’ve just downloaded the .msi again and installed it, but the problem still occures.

1 Like

Same question as afischer211. Since DockerForWindows cannot complete initialization it won’t auto-update, will it?
below: beginning of log file (this thing grows fast)

> [11:40:50.015][Program        ][Info   ] Version 1.11.1-beta11 (build: 2744)
> [11:40:50.016][Program        ][Info   ] Starting on: 5/11/2016 11:40:50 AM
> [11:40:50.016][Program        ][Info   ] Resources: C:\Program Files\Docker\Docker\Resources
> [11:40:50.017][Program        ][Info   ] OS: Windows 10 Pro
> [11:40:50.017][Program        ][Info   ] Edition: Professional
> [11:40:50.017][Program        ][Info   ] Id: 1511
> [11:40:50.017][Program        ][Info   ] Build: 10586
> [11:40:50.018][Program        ][Info   ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908
> [11:40:50.022][Program        ][Info   ] Mixpanel Id: 483A3382-E1B8-4CE4-A034-5D1972F468B5
> [11:40:50.023][Program        ][Info   ] Sha1: 51937ce6b9f8f70c9a642f493d63db1521a4fb7d
> [11:40:50.023][Program        ][Info   ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
> [11:40:50.122][Mixpanel       ][Info   ] Tracking: appLaunched
> [11:40:50.811][Mixpanel       ][Info   ] Tracking: heartbeat
> [11:40:50.812][BackendServer  ][Info   ] Started
> [11:40:50.815][NamedPipeServer][Error  ] Pipe failure: Impossible de traduire certaines ou toutes les références d'identité.    à System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
>    à System.Security.Principal.NTAccount.Translate(Type targetType)
>    à System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
>    à System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
>    à Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
>    à Docker.Core.pipe.NamedPipeServer.Run()
> [11:40:50.816][NamedPipeServer][Error  ] Pipe failure: Impossible de traduire certaines ou toutes les références d'identité.    à System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
>    à System.Security.Principal.NTAccount.Translate(Type targetType)
>    à System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
>    à System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
>    à Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
>    à Docker.Core.pipe.NamedPipeServer.Run()
> [11:40:50.816][NamedPipeServer][Error  ] Pipe failure: Impossible de traduire certaines ou toutes les références d'identité.    à System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
>    à System.Security.Principal.NTAccount.Translate(Type targetType)
>    à System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
>    à System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
>    à Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
>    à Docker.Core.pipe.NamedPipeServer.Run()
1 Like

Hello,

Got the same problem, I tried:

Removing the VM manually
Uninstalled docker
Rebooted
Installed docker

The VM gets created again but it wont start and “Docker is initializing…” in tray.

Best
//Dennis

Will the auto update work even if docker gets stuck on “initializing” ([NamedPipeServer][Error ] Pipe failure …)?
If not, can you post a link to download?

Thank you.
Best regards,
Z.

I am still getting the same error, using the updated fix.

Same error as before, here is the current log:
[21:04:32.098][Program ][Info ] Version 1.11.1-beta11 (build: 2789)
[21:04:32.105][Program ][Info ] Starting on: 5/11/2016 9:04:32 PM
[21:04:32.109][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[21:04:32.115][Program ][Info ] OS: Windows 10 Pro Insider Preview
[21:04:32.123][Program ][Info ] Edition: Professional
[21:04:32.127][Program ][Info ] Id: 1511
[21:04:32.133][Program ][Info ] Build: 14332
[21:04:32.139][Program ][Info ] BuildLabName: 14332.1001.amd64fre.rs1_release.160422-1940
[21:04:32.146][Program ][Info ] Mixpanel Id: B6398489-9451-45D9-9575-DBDDFB0FAF12
[21:04:32.152][Program ][Info ] Sha1: b0bc231ec0337a84cc1ce50f51df77f9b0f5c993
[21:04:32.157][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[21:04:33.974][Mixpanel ][Info ] Tracking: appLaunched
[21:04:34.392][Mixpanel ][Info ] Tracking: heartbeat
[21:04:34.397][BackendServer ][Info ] Started
[21:04:34.533][NamedPipeClient][Info ] Sending Version()…
[21:04:34.546][NamedPipeServer][Info ] Version()
[21:04:34.551][NamedPipeServer][Info ] Version done.
[21:04:34.561][NamedPipeClient][Info ] Received response for Version: Version 1.11.1-beta11 (build: 2789)
[21:04:34.566][NamedPipeClient][Info ] Sending CheckInstallation()…
[21:04:34.572][NamedPipeServer][Info ] CheckInstallation()
[21:04:34.576][HyperV ][Info ] Check Hyper-V Windows optional feature
[21:04:34.583][PowerShell ][Info ] Run script…
[21:04:35.741][HyperV ][Info ] Hyper-V Windows feature is enabled
[21:04:35.747][NamedPipeServer][Info ] CheckInstallation done.
[21:04:35.753][NamedPipeClient][Info ] Received response for CheckInstallation:
[21:04:35.762][NamedPipeClient][Info ] Sending CheckHyperVState()…
[21:04:35.768][NamedPipeServer][Info ] CheckHyperVState()
[21:04:35.775][HyperV ][Info ] Check Hyper-V Service State
[21:04:35.808][PowerShell ][Info ] Run script with parameters: -Check True…

How did you get the fix? I see the new build-version 2789 instead of 2744

Try redownloading the beta installer, and install it again. This fixed it for me

5 Likes

“redownloading the beta installer, and install it again”

Thank you. It solved my problem.

1 Like

Re-downloaded and chose repair, its running now thanks.

1 Like

Looking at the difference between old and new, it looks like some usernames and passwords have been quoted in MobyLinux.ps1. While that may fix the NTAccount/NamedPipeServer issue, I don’t believe it fixes the original issue - my docker is still getting stuck at the same point:

[22:26:03.042][NamedPipeClient][Info   ] Received response for Version: Version 1.11.1-beta11 (build: 2789)
[22:26:03.058][NamedPipeClient][Info   ] Sending CheckInstallation()...
[22:26:03.058][NamedPipeServer][Info   ] CheckInstallation()
[22:26:03.058][HyperV         ][Info   ] Check Hyper-V Windows optional feature
[22:26:03.058][PowerShell     ][Info   ] Run script...
[22:26:03.759][HyperV         ][Info   ] Hyper-V Windows feature is enabled
[22:26:03.762][NamedPipeServer][Info   ] CheckInstallation done.
[22:26:03.765][NamedPipeClient][Info   ] Received response for CheckInstallation:
[22:26:03.768][NamedPipeClient][Info   ] Sending CheckHyperVState()...
[22:26:03.770][NamedPipeServer][Info   ] CheckHyperVState()
[22:26:03.774][HyperV         ][Info   ] Check Hyper-V Service State
[22:26:03.780][PowerShell     ][Info   ] Run script with parameters: -Check True...
C:\Program Files\Docker\Docker\resources>
2 Likes

“redownloading the beta installer, and install it again”

Thank you. It solved also my problem. Now all is running again (and I will test further).

1 Like

Solved for me too, new msi installer has the fix. Thanks!

1 Like

Suffering the same issue with a clean install of the latest build

[22:50:12.761][Program ][Info ] Version 1.11.1-beta11 (build: 2789)
[22:50:12.772][Program ][Info ] Starting on: 5/11/2016 10:50:12 PM
[22:50:12.777][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[22:50:12.784][Program ][Info ] OS: Windows 10 Pro Insider Preview
[22:50:12.788][Program ][Info ] Edition: Professional
[22:50:12.793][Program ][Info ] Id: 1511
[22:50:12.799][Program ][Info ] Build: 14332
[22:50:12.804][Program ][Info ] BuildLabName: 14332.1001.amd64fre.rs1_release.160422-1940
[22:50:12.832][Program ][Info ] Mixpanel Id: 7B37CA34-8584-4ED2-B57B-20E3D930A488
[22:50:12.843][Program ][Info ] Sha1: b0bc231ec0337a84cc1ce50f51df77f9b0f5c993
[22:50:12.848][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[22:50:13.595][Mixpanel ][Info ] Tracking: appLaunched
[22:50:16.519][Mixpanel ][Info ] Tracking: heartbeat
[22:50:16.550][BackendServer ][Info ] Started
[22:50:16.680][NamedPipeClient][Info ] Sending Version()…
[22:50:16.696][NamedPipeServer][Info ] Version()
[22:50:16.706][NamedPipeServer][Info ] Version done.
[22:50:16.723][NamedPipeClient][Info ] Received response for Version: Version 1.11.1-beta11 (build: 2789)
[22:50:16.730][NamedPipeClient][Info ] Sending CheckInstallation()…
[22:50:16.734][NamedPipeServer][Info ] CheckInstallation()
[22:50:16.744][HyperV ][Info ] Check Hyper-V Windows optional feature
[22:50:16.753][PowerShell ][Info ] Run script…
[22:50:21.716][HyperV ][Info ] Hyper-V Windows feature is enabled
[22:50:21.723][NamedPipeServer][Info ] CheckInstallation done.
[22:50:21.728][NamedPipeClient][Info ] Received response for CheckInstallation:
[22:50:21.733][NamedPipeClient][Info ] Sending CheckHyperVState()…
[22:50:21.738][NamedPipeServer][Info ] CheckHyperVState()
[22:50:21.744][HyperV ][Info ] Check Hyper-V Service State
[22:50:21.813][PowerShell ][Info ] Run script with parameters: -Check True…

Tested by myself.

After last update, fixed the issue.

Version 1.11.1-beta11 (build: 2789) fixed :slight_smile:

As @silarsis said, I think multiple issues have been reported under this thread.

The original issue reported by @kalvinmoraes appears to still be there, with version 1.11.1-beta11 (build: 2789).
This issue is why I am still subscribed to this thread.

1 Like

Frech download ans install. Problem still exists with build 14332.

Are you looking at the issue where Docker initialize gets stuck at the line (from teh original post):

[11:03:57.407][PowerShell ][Info ] Run script with parameters: -Check True…

Looks like it affects insider builds. I look forward to being able to test the beta docker for windows. :slight_smile:

Confirming problem still exists with build 14342, even after fresh install.

I upgraded to 14342 and am now getting a different problem (the MSFT_NetAdapter one).

For the record, this thread (http://www.thomasmaurer.ch/2015/11/hyper-v-virtual-switch-using-nat-configuration/) appears to suggest that the NAT VMSwitch type has been removed in recent versions of Win10 - I suspect this is the underlying issue for both the MSFT_NetAdapter and the -Check true freeze, given the freeze started about when the Nat vmswitch was removed…

MSFT_NetAdapter problem partially solved in another thread, but it leads back to the -Check freeze problem.

Also as a note, if you comment out the “Check-HyperV” call in MobyLinux.ps1 (just return $true) you get exactly the same freeze after the -Check call - so I think it’s whatever happens directly after that that’s causing the problem. To the best of my knowledge, the code isn’t available for this?

I still can’t get DHCP happening on the internal switch - was working on the theory that was handled by the docker for windows software itself, but can’t get past that -Check freeze.