Useful or not, from you.
for-win Docker desktop is failing to start with the error 'Timed out waiting for the lifecycle-server to start.'

<!-- Please, check https://docs.docker.com/docker-for-windows/troubleshoot/. Issues without logs and details cannot be debugged and will be closed.

Issues unrelated to Docker Desktop will be closed. In particular, see

  • https://github.com/moby/moby/issues for Docker daemon, e.g. running on Windows Server with Docker EE
  • https://github.com/docker/compose/issues for docker-compose
  • https://github.com/docker/machine/issues for docker-machine
  • https://github.com/docker/docker.github.io/issues for the documentation -->

<!-- Replace - [ ] with - [x], or click after having submitted the issue. --> <!-- Download Docker Desktop 'Edge' (latest build) here: https://hub.docker.com/editions/community/docker-ce-desktop-windows -->

  • [x] I have tried with the latest version of my channel (Stable or Edge)
  • [x] I have uploaded Diagnostics
  • Diagnostics ID: 74EA6B74-804D-43A1-8DB9-09010615B4F2/20190826180252

Expected behavior

After a clean install, docker desktop should start, but it's not starting.

Actual behavior

Getting the following error message, which is hard to debug.

Timed out waiting for the lifecycle-server to start.
This may be the result of a slow environment or there may be a real problem.
This timeout can be increased by editing settings.json, value 'lifecycleTimeoutSeconds'.
This file is usually in C:\Users\(your username)\AppData\Roaming\Docker

   at Docker.Core.Pipe.NamedPipeClient.<TrySendAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
   at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup)
   at Docker.Actions.<>c__DisplayClass24_0.<Start>b__0()
   at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass17_0.<.ctor>b__1()

log.txt

Information

<!-- Please, help us understand the problem. For instance:

  • Is it reproducible?
  • Is the problem new?
  • Did the problem appear with an update?
  • A reproducible case if this is a bug, Dockerfiles with reproduction inside is best. -->
  • Windows Version: Windows 10 Enterprise (Id: 1803, Build: 17134). This is a windows 10 VM hosted on VMWare vsphere.
  • Docker Desktop Version: 2.1.0.1

Before few weeks, everything was working fine. I think, I tried to update docker or restarted the machine and then it has stopped working.

I have tried with 2.0.0.3 and 2.1.0.1 stable installers but none of those are working and giving same errors. I tried increasing memory, enabling/disabling hyper-v but none of those has helped yet.

Steps to reproduce the behavior

<!-- A reproducible case, Dockerfiles with reproduction inside is best. -->

  1. Clean install/reinstall
  2. Start docker desktop.
That's a useful answer
Without any help

Mac Parallels 13.3.2, Windows 10 pro 1903 virtual machine

  • Stable 2.1.0.1 doesn't work
  • Stable 2.0.0.3 doesn't work (as suggested here #4393)

Both versions have same issue virtual machine in Hyper-V consumes 50% host CPU and never gets ready to work.

  • Changing VM settings in (more memory or more CPU-s ) doesn't have any effect.
  • Extending lifecycle timeout up to 600s doesn't have any effect

However latest Edge release: Docker Desktop Community 2.1.1.0 (37260) works, starts within 10s Also I have selected inside Edge version installation to install missing windows components not sure if this made difference or what exactly changes in Win.

I have disabled docker desktop auto start on OS startup, hate having apps running that I don't use so I can't confirm if starts within 10s when OS is starting.

Hope this helps.

@gljubojevic thanks a lot for your reply with instructions. I tried with 2.1.1.0 edge version and checked 'install missing windows components' during the installation. And that did the trick. It worked now. Thanks again.