Skip to content

Docker failed to start in 4.1.1 Linux Container #12270

Closed
Closed
Docker failed to start in 4.1.1 Linux Container#12270
Labels
lifecycle/locked

Description

@soroshsabz
soroshsabz
opened on Oct 14, 2021

ITNOA

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: 5BCDC324-A8CA-44F2-9CDA-DE2A62E609EB/20211014120311

Actual behavior

When I switch to Linux container I see below exception

System.InvalidOperationException:
Failed to deploy distro docker-desktop to C:\Users\ssoroosh\AppData\Local\Docker\wsl\distro: exit code: -1
 stdout: The network was not found.


 stderr: 
   at Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:line 146
   at Docker.Engines.WSL2.WSL2Provisioning.<DeployDistroAsync>d__17.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 168
--- 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 Docker.Engines.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 77
--- 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 Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__29.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:line 194
--- 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 Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29
--- 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 Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92

Expected behavior

I expect docker switch to linux container correctly, without any error.

Information

Please, help us understand the problem. For instance:

  • Is it reproducible? Yes

  • Is the problem new? No, from version 4.0.0 related to Docker Engine failed to start #12066

  • Did the problem appear with an update? No (but this problem is occur when I install new Windows Cumulative Update 2021/09

  • Windows Version: Windows 10 Version 21H1 (OS Build 19043.1237)

  • Windows Feature Experience Pack: 120.2212.3530.0

  • Docker Desktop Version: 4.1.1

  • WSL2 or Hyper-V backend? I use Windows Container (but WSL 2 based engine is enable in setting)

  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

My docker settings like below

{
  "registry-mirrors": [],
  "insecure-registries": [],
  "debug": false,
  "experimental": false
}

Steps to reproduce the behavior

  1. Try to run Docker Desktop
  2. Docker Desktop try to start Docker Engine
  3. Docker Engine failed to start after couple of minutes
  4. I cannot do anything :(

Activity

  1. soroshsabz commented on Oct 14, 2021

    @soroshsabz
    soroshsabz
    on Oct 14, 2021
    Author
    Please investigate the following 3 issues:

1 : are the LinuxKit services running?
    Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

2 : are the backend processes running?
    Failed with: 4 errors occurred:
        * vpnkit-bridge.exe is not running
        * vpnkit.exe is not running
        * com.docker.proxy.exe is not running
        * com.docker.wsl-distro-proxy.exe is not running


Not all of the backend processes are running.

3 : is the VM networking working?
    Failed with: network checks failed: Post "http://ipc/check-network-connectivity": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.

    How to resolve these issue?

  2. Imagesoroshsabz
    changed the title [-]Docker failed to start in 4.1.1 with WSL[/-] [+]Docker failed to start in 4.1.1 Linux Container[/+] on Oct 14, 2021

  3. soroshsabz commented on Oct 14, 2021

    @soroshsabz
    soroshsabz
    on Oct 14, 2021
    Author

    /version 4.1.1

  4. psantos10 commented on Oct 15, 2021

    @psantos10
    psantos10
    on Oct 15, 2021

    I also keep having the same issue related here: #12229

    It started when I upgraded to 4.1.0. To solve the issue, the only solution was downgrade to 4.0.1.

    Now, with 4.1.1, I upgraded, and at the time, it was working. But after restarting the PC the problem appears again.

    I cleanup everything. Deleted all docker related files and directory, and installed docker again. Again, was working but after restarting the PC, the problem still there.

    image

    Diagnostics ID: 4C300C44-6CBC-497C-A809-ED0E1440597E/20211015102406

  5. aimeeso commented on Oct 25, 2021

    @aimeeso
    aimeeso
    on Oct 25, 2021

    I encountered the same issue as well. I am using v4.1.1 and wsl2.

    The follwing info and warning are repeating forever.
    [10:43:07.162][IPCClient ][Info ] (3c7b1b07) 8efe7570-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [10:43:08.169][WslIntegrationService][Warning] HttpOS Client: connection timed out.

    Diagnostics ID: 8C789F0F-4B0E-4573-BC37-E9549F25A2CE/20211025024102

  6. soroshsabz commented on Oct 28, 2021

    @soroshsabz
    soroshsabz
    on Oct 28, 2021
    Author

    This version does not work for Windows Container too

    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-16599\src\github.com\docker\pinata\win\src\Docker.Backend\Processes\WindowsDockerDaemon.cs:line 212
   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()

  7. soroshsabz commented on Nov 5, 2021

    @soroshsabz
    soroshsabz
    on Nov 5, 2021
    Author

    Any update or workaround?

  8. Imagesoroshsabz
    closed this as completedon Dec 31, 2021

  9. docker-robott commented on Jan 30, 2022

    @docker-robott
    docker-robott
    on Jan 30, 2022
    Collaborator

    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

  10. Imagedocker
    locked and limited conversation to collaborators on Jan 30, 2022
  11. Imagedocker-robott
    added
    lifecycle/locked
    on Jan 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/locked

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions