I downloaded docker for windows, and installed it. I then started docker and then did Switch to Windows containers form the taskbar tray, but I get error message. i downlaoded and installed 3.5.2
I was getting the same error for version 3.6
System.ServiceProcess.TimeoutException:
Time out has expired and the operation has not been completed.
at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
at Docker.Backend.Processes.WindowsDockerDaemon.TryToStartService(Settings settings, String args, Dictionary`2 env) in C:\workspaces\PR-16070\src\github.com\docker\pinata\win\src\Docker.Backend\Processes\WindowsDockerDaemon.cs:line 208
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass6_1.<GetExecutor>b__0(Object instance, Object[] methodParameters)
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__15.MoveNext()
Had to rip out antivirus just to get docker to even install. It switched to windows containers once and then hasnāt sinceā¦
I get the same exact issue posted before. Same steps to reproduce. Iāve tried Docker 3.6 and 3.5.2. Iām about to go into older versions because I need this working.
Linux containers run just fine
Could this be because of bitlocker enabled on this computer?
The Windows container was able to be started and the worked normally only once. After a normal reboot, the Docker (Windows container mode) failed to start. After re-install the Docker, only the Linux container engine (Hyper-V/WSL2) could be started.
This really drove me crazyā¦ After trail-n-error for several configuration for over 18 hours, it keeping failure at second bootā¦ no matter Iām using what computer, or VM.
I just use the āresmonā to watch the starting behavior of the Docker Desktop, no significantly problem, the traffic is not blocked by firewall also.
I found few articles mentioned the vEthernet (nat) may not be started automatically after Windows reboot, this phenomenon is similar from my case, the āturn-on of Windows Containerā will create the āvEthernet (nat)ā and the Windows container does well even I restart Docker several times:
And then, those virtual ethernet card are gone after reboot:
I donāt know if this is correct direction, I even compared the Windows Registry, the major difference after turning on the Windows container is some ethernet settings.
Thank you very much for this solution. Yes, it worked for me. I unchecked the āRead-Onlyā on the panic.txt file and then did the switch to windows containers, and it switched successfully.
I stumbled upon a post after carefully going through all git issues that seemed similar, it was buried a bit more down already with not a lot of traction on the thread. So little bit of luck
