Docker not initializing after update

kalvinmoraes · May 5, 2016, 2:21pm

Expected behavior

Docker should start and give me a notification about it.

Actual behavior

The systray icon keeps on “Docker is initializing…” and nothing else happens.

Information

The last update from Docker for Windows keeps showing me “Docker is initializing” forever.

Before the update, it starts just ok, but now, after the update, don’t.

I’ve noticed that it creates the MobyLinuxVM successfully, but it seems that Docker could not start it.

Even starting the VM by myself through Hyper-V, it seems Docker can’t communicate with it.

Executing “DockerDebugInfo.ps1” on Powershell returns an error saying that the command doesn’t exists.

Here’s the log from AppData/Local. It doesn’t show more than that.

[11:03:55.209][Program ][Info ] Version 1.11.1-beta10 (build: 2446)
[11:03:55.210][Program ][Info ] Starting on: 5/5/2016 11:03:55 AM
[11:03:55.210][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[11:03:55.211][Program ][Info ] OS: Windows 10 Pro Insider Preview
[11:03:55.211][Program ][Info ] Edition: Professional
[11:03:55.212][Program ][Info ] Id: 1511
[11:03:55.212][Program ][Info ] Build: 14332
[11:03:55.212][Program ][Info ] BuildLabName: 14332.1001.amd64fre.rs1_release.160422-1940
[11:03:55.215][Program ][Info ] Mixpanel Id: 73eec41f-7a2a-44a2-9d5a-92f430b6e688
[11:03:55.216][Program ][Info ] Sha1: 51937ce6b9f8f70c9a642f493d63db1521a4fb7d
[11:03:55.216][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[11:03:55.392][Mixpanel ][Info ] Tracking: appLaunched
[11:03:56.364][Mixpanel ][Info ] Tracking: heartbeat
[11:03:56.687][BackendServer ][Info ] Started
[11:03:56.718][NamedPipeServer][Info ] CheckInstallation:[]
[11:03:56.719][HyperV ][Info ] Check Hyper-V Windows optional feature
[11:03:56.720][PowerShell ][Info ] Run script…
[11:03:57.398][HyperV ][Info ] Hyper-V Windows feature is enabled
[11:03:57.398][NamedPipeServer][Info ] CheckInstallation done.
[11:03:57.400][NamedPipeServer][Info ] CheckHyperVState:[]
[11:03:57.400][HyperV ][Info ] Check Hyper-V Service State
[11:03:57.407][PowerShell ][Info ] Run script with parameters: -Check True…

Steps to reproduce the behavior

Download Docker for Windows from Docker.com or update it from the old versions (from 2, 3 days ago)
Install it / Update it.
Start Docker for Windows
Wait forever, nothing else happens

kalvinmoraes · May 5, 2016, 4:37pm

Solved by quitting Windows Insiders.

renomarcello · May 6, 2016, 3:52pm

Exactly the same problem here - all exactly as above (i.e. same whether installed fresh or upgrade from beta 9):

[16:57:49.190][Program ][Info ] Version 1.11.1-beta10 (build: 2446)
[16:57:49.202][Program ][Info ] Starting on: 5/6/2016 4:57:49 PM
[16:57:49.206][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[16:57:49.211][Program ][Info ] OS: Windows 10 Pro Insider Preview
[16:57:49.219][Program ][Info ] Edition: Professional
[16:57:49.229][Program ][Info ] Id: 1511
[16:57:49.236][Program ][Info ] Build: 14332
[16:57:49.243][Program ][Info ] BuildLabName: 14332.1001.amd64fre.rs1_release.160422-1940
[16:57:49.306][Program ][Info ] Mixpanel Id: F3AF861C-8719-42CE-A74F-E057BFB179BD
[16:57:49.318][Program ][Info ] Sha1: 51937ce6b9f8f70c9a642f493d63db1521a4fb7d
[16:57:49.337][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[16:57:49.621][Mixpanel ][Info ] Tracking: appLaunched
[16:57:49.980][Mixpanel ][Info ] Tracking: heartbeat
[16:57:50.227][BackendServer ][Info ] Started
[16:57:50.264][NamedPipeServer][Info ] CheckInstallation:[]
[16:57:50.270][HyperV ][Info ] Check Hyper-V Windows optional feature
[16:57:50.275][PowerShell ][Info ] Run script…
[16:57:51.800][HyperV ][Info ] Hyper-V Windows feature is enabled
[16:57:51.804][NamedPipeServer][Info ] CheckInstallation done.
[16:57:51.810][NamedPipeServer][Info ] CheckHyperVState:[]
[16:57:51.828][HyperV ][Info ] Check Hyper-V Service State
[16:57:51.837][PowerShell ][Info ] Run script with parameters: -Check True…

kalvinmoraes · May 6, 2016, 4:51pm

Hi Reno.

Thanks for your feedback. Glad to hear that I’m not crazy about this.

It seems that by being part of Windows Insiders give us an update that somehow conflicts with the Hyper-V.

I’ve noticed some weird behaviors after quitting Insiders and finished by
formatting my entire computer just in case.

Now I’m running Windows 10 Pro x64, Hyper-V activated and WITHOUT being part of Windows Insiders.

It’s working just fine now.

Hope it helps.

Cheers,

russlescai · May 9, 2016, 1:06am

I am experiencing the same error too.

FYI, I am in the fast track, build 14332.rs1_release.160422-1940.

I thought it may have been due to having other VM’s setup in Hyper-V already.

Look forward to some feedback as to when this will be fixed (let me know if you need more details!)

Also - this was a fresh install (not an update), as I have only been a private beta member for a couple of days.

This is my log file:
[20:29:25.710][Program ][Info ] Version 1.11.1-beta10 (build: 2446)
[20:29:25.721][Program ][Info ] Starting on: 5/9/2016 8:29:25 PM
[20:29:25.729][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[20:29:25.740][Program ][Info ] OS: Windows 10 Pro Insider Preview
[20:29:25.751][Program ][Info ] Edition: Professional
[20:29:25.761][Program ][Info ] Id: 1511
[20:29:25.770][Program ][Info ] Build: 14332
[20:29:25.777][Program ][Info ] BuildLabName: 14332.1001.amd64fre.rs1_release.160422-1940
[20:29:25.806][Program ][Info ] Mixpanel Id: B6398489-9451-45D9-9575-DBDDFB0FAF12
[20:29:25.815][Program ][Info ] Sha1: 51937ce6b9f8f70c9a642f493d63db1521a4fb7d
[20:29:25.821][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[20:29:26.380][Mixpanel ][Info ] Tracking: appLaunched
[20:29:27.287][Mixpanel ][Info ] Tracking: heartbeat
[20:29:28.448][BackendServer ][Info ] Started
[20:29:28.520][NamedPipeServer][Info ] CheckInstallation:[]
[20:29:28.530][HyperV ][Info ] Check Hyper-V Windows optional feature
[20:29:28.551][PowerShell ][Info ] Run script…
[20:29:30.040][HyperV ][Info ] Hyper-V Windows feature is enabled
[20:29:30.045][NamedPipeServer][Info ] CheckInstallation done.
[20:29:30.053][NamedPipeServer][Info ] CheckHyperVState:[]
[20:29:30.059][HyperV ][Info ] Check Hyper-V Service State
[20:29:30.072][PowerShell ][Info ] Run script with parameters: -Check True…

russlescai · May 9, 2016, 11:33am

Stopping being an insider doesn’t revert your Windows version back to a previous version…the issue still occurs.

silarsis · May 10, 2016, 12:27am

I’m getting the same issue - I’ve been a docker on windows beta user for a while (and also an insider), and something in a recent update of windows appears to have killed docker. Interestingly, while I have the same logs, running the MobyLinux.ps1 script with -Check in an admin powershell window works fine - it comes back reporting Hyper-V is fine.

If I use the MobyLinux.ps1 script to -Create and -Start, I get a VM but it doesn’t get an IP. I’m unclear on exactly how the IP is allocated to the VM once it comes up, so am struggling to debug further than this.

russlescai · May 10, 2016, 12:36am

Yeah, I tried the same - running the MobyLinux.ps1 -Check worked fine too.

I checked the MobyNAT network adapter had been setup and attached, and the Get-NetNat showed the NAT config had been completed too.

Look forward to getting my hands dirty(ier) with the beta soon!

kalvinmoraes · May 10, 2016, 7:53pm

Sure, but it’s weird because after I’ve did a fresh Windows 10 install it worked just fine.

Now, with the last update, again, it stopped working.

I’ll try to dig on this today.

Thanks for your feedback!

kalvinmoraes · May 10, 2016, 8:11pm

So, after uninstalling and installing Docker again. Now I’m getting the following error on my log file:

[17:07:42.141][NamedPipeServer][Error ] Pipe failure: Não foi possível converter algumas ou todas as referências de identidade. em System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) em System.Security.Principal.NTAccount.Translate(Type targetType) em System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) em System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule) em Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName) em Docker.Core.pipe.NamedPipeServer.Run()

Unfortunately it’s in Portuguese (since it’s my native language).

“Não foi possível converter algumas ou todas as referências de identidade” -> “It’s not possible to convert some/all identity references”

Any clue? Maybe it’s something about my account name?

tvollstaedt · May 10, 2016, 9:57pm

Same issue here. Updated today to new Docker Beta, now I’m getting the same issue. Docker is always “initializing”. Tried Repair, Uninstall, Removing Hyper-V Machine, Hyper-V Server, Installing last working Docker version (Beta10). The error persists.

My Logfile:

[23:46:47.113][Program ][Info ] Version 1.11.1-beta11 (build: 2744) [23:46:47.113][Program ][Info ] Starting on: 5/10/2016 11:46:47 PM [23:46:47.113][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources [23:46:47.128][Program ][Info ] OS: Windows 10 Pro [23:46:47.128][Program ][Info ] Edition: Professional [23:46:47.128][Program ][Info ] Id: 1511 [23:46:47.128][Program ][Info ] Build: 10586 [23:46:47.128][Program ][Info ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908 [23:46:47.159][Program ][Info ] Mixpanel Id: CC0C210E-8868-42AF-BCF4-0CCE780BF30A [23:46:47.175][Program ][Info ] Sha1: 436d388f84b51eac1ea0d076f5b6bdc703348800 [23:46:47.175][Program ][Info ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows [23:46:47.284][Mixpanel ][Info ] Tracking: appLaunched [23:46:47.784][Mixpanel ][Info ] Tracking: heartbeat [23:46:47.784][BackendServer ][Info ] Started [23:46:47.800][NamedPipeServer][Error ] Pipe failure: Manche oder alle Identitätsverweise konnten nicht übersetzt werden. bei System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) bei System.Security.Principal.NTAccount.Translate(Type targetType) bei System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) bei System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule) bei Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName) bei Docker.Core.pipe.NamedPipeServer.Run() [23:46:47.800][NamedPipeServer][Error ] Pipe failure: Manche oder alle Identitätsverweise konnten nicht übersetzt werden. bei System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) bei System.Security.Principal.NTAccount.Translate(Type targetType) bei System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) bei System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule) bei Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName) bei Docker.Core.pipe.NamedPipeServer.Run() ...

German error message means: “Identity failure: Some identity reference could not be translated” (Whatever this means).

jcaridemobail · May 10, 2016, 10:00pm

Hi!

I’ve just updated Docker for Windows to the last versión and after the upgrade Docker didn’t starts properly it is always in “initializing” state. I’ve tried to Uninstall, reboot and install agay and the error is still there.

Here is my logfile:

[23:42:46.289][Program        ][Info   ] Version 1.11.1-beta11 (build: 2744)
[23:42:46.289][Program        ][Info   ] Starting on: 5/10/2016 11:42:46 PM
[23:42:46.289][Program        ][Info   ] Resources: C:\Program Files\Docker\Docker\Resources
[23:42:46.289][Program        ][Info   ] OS: Windows 10 Pro
[23:42:46.289][Program        ][Info   ] Edition: Professional
[23:42:46.305][Program        ][Info   ] Id: 1511
[23:42:46.305][Program        ][Info   ] Build: 10586
[23:42:46.305][Program        ][Info   ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908
[23:42:46.305][Program        ][Info   ] Mixpanel Id: FD2F1C32-D106-40F9-A0AA-D3F7CB698CBA
[23:42:46.305][Program        ][Info   ] Sha1: 436d388f84b51eac1ea0d076f5b6bdc703348800
[23:42:46.320][Program        ][Info   ] You can send feedback, including this log file, at https://forums.docker.com/c/docker-for-windows
[23:42:46.461][Mixpanel       ][Info   ] Tracking: appLaunched
[23:42:47.289][Mixpanel       ][Info   ] Tracking: heartbeat
[23:42:47.289][BackendServer  ][Info   ] Started
[23:42:47.305][NamedPipeServer][Error  ] Pipe failure: No se pudieron convertir algunas o todas las referencias de identidad.    en System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   en System.Security.Principal.NTAccount.Translate(Type targetType)
   en System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   en System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
   en Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
   en Docker.Core.pipe.NamedPipeServer.Run()
[23:42:47.305][NamedPipeServer][Error  ] Pipe failure: No se pudieron convertir algunas o todas las referencias de identidad.    en System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   en System.Security.Principal.NTAccount.Translate(Type targetType)
   en System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   en System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
   en Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
   en Docker.Core.pipe.NamedPipeServer.Run()
[23:42:47.305][NamedPipeServer][Error  ] Pipe failure: No se pudieron convertir algunas o todas las referencias de identidad.    en System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   en System.Security.Principal.NTAccount.Translate(Type targetType)
   en System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   en System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
   en Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
   en Docker.Core.pipe.NamedPipeServer.Run()

kalvinmoraes · May 10, 2016, 10:05pm

Hi!

Receiving the same error here:

[19:04:28.574][NamedPipeServer][Error  ] Pipe failure: Some or all identity references could not be translated.    at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   at System.Security.AccessControl.CommonObjectSecurity.SetAccessRule(AccessRule rule)
   at Docker.Core.pipe.NamedPipeServer.NewPipeServer(String pipeName)
   at Docker.Core.pipe.NamedPipeServer.Run()

mariosanroman · May 11, 2016, 1:32am

Same pipe failure here.

pmario · May 11, 2016, 6:35am

I did try to uninstall and install docker4windows. -> doesn’t solve the problem.
windows restart -> doesn’t solve the problem.

etomilin · May 11, 2016, 7:39am

Same problem. Uninstalling and installing again did not solved it. Reverting to beta 10 did.

dgageot · May 11, 2016, 7:45am

If someone here in europe can ping me (david.gageot@docker.com), I’ll send you a test bug fix release

dgageot · May 11, 2016, 8:08am

Looks like we have a fix. We’re going to release a hotfix this morning (Paris time)

dgageot · May 11, 2016, 8:55am

The fix was pushed and should be available through the auto-update mechanism. Thank you all for the feedback and sorry for the inconvenience.

afischer211 · May 11, 2016, 9:22am

How can I download the fix manually? Becaue of not coming to end for init the docker-trayicon can not call autoupdate…

Topic		Replies	Views
Docker for Windows does not start after reinstall Docker Desktop docker , windows	4	2662	August 7, 2016
MobyLinux could not be started because the hypervisor is not running. WIN10 Docker Desktop docker , beta , windows	3	3123	July 19, 2016
Docker for Windows does not start Docker Desktop windows	8	8096	May 3, 2016
Updated to 1.12.0-stable and no longer works Docker Desktop docker	6	1512	September 1, 2016
Docker cannot contact the hypervisor and the VM cannot start Docker Desktop windows	2	2572	May 28, 2016

Docker not initializing after update

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

Related topics