Skip to content

Starting the Docker Engine loop - There was a problem with WSL crash #772

Open

Description

@manel00

Bug report

running wslexec: An error occurred while running the command. DockerDesktop/Wsl/ExecError: c:\windows\system32\wsl.exe -d docker-desktop -u root -e wsl-bootstrap run --base-image <home>/appdata/local/programs/dockerdesktop/resources/docker-desktop.iso --cli-iso <home>/appdata/local/programs/dockerdesktop/resources/wsl/docker-wsl-cli.iso --data-disk 59bbd5c8-c759-0f4a-b74c-0b6563a9b579: exit status 1 (stderr: [2026-10-22T11:28:32.443852708Z][wsl-bootstrap.version][W] failed to read component versions: open /opt/docker-desktop/componentsVersion.json: no such file or directory
[2026-10-22T11:28:32.445832369Z][wsl-bootstrap] provisioning data via data disk with id: 59bbd5c8-c759-0f4a-b74c-0b6563a9b579
[2026-10-22T11:28:32.446687640Z][wsl-bootstrap] pre-bootstrap complete
[2026-10-22T11:28:32.524933149Z][wsl-bootstrap] detected existing ext4 file system
Error: preparing environment: mounting cli-tools iso: ensuring drive c is mounted: running mount -t drvfs c:\ /tmp/host/c -o noatime: <3>WSL (27 - ) ERROR: UtilConnectVsock:618: connect port 50002 failed 110 (from: int MountPlan9Share(const char *, const char *, const char *, bool, int *)[drvfs.cpp:586])
: exit status 32
[2026-10-22T11:29:04.206049359Z][wsl-bootstrap][F] preparing environment: mounting cli-tools iso: ensuring drive c is mounted: running mount -t drvfs c:\ /tmp/host/c -o noatime: <3>WSL (27 - ) ERROR: UtilConnectVsock:618: connect port 50002 failed 110 (from: int MountPlan9Share(const char *, const char *, const char *, bool, int *)[drvfs.cpp:586])
: exit status 32
[main.main()
[	linuxkit/pkg/desktop/wsl-bootstrap/main.go:66 +0x111
, stdout: , wslErrorCode: DockerDesktop/Wsl/ExecError)

Platform

Windows 11

Version information

Docker Desktop: 4.96.0 and 4.87.0
WSL 3.0.3

Diagnostics ID

No response

Closing Docker Desktop, wsl --shutdown and then initialize, does not work

Activity

  1. added theissue type on Oct 22, 2026
  2. voonyee commented on Oct 23, 2026

    @voonyee
    Collaborator

    Hi, and thanks for the report. Sorry that your Docker Desktop won't start.

    There are some other people have hit the same error, and in some cases it was caused by Windows permissions or security software on the machine. See the workaround here: docker/for-win#14856 (comment)

    Can you try the workaround to see if it helps?

    May I know if Docker Desktop successfully started on this machine before?

  3. manel00 commented on Oct 23, 2026

    @manel00
    Author

    Yes It was working perfectly until an update from Windows 11, my laptop has corporation environment settings.

    Executing docker desktop start on PS run as admin it does NOT work for me...

  4. voonyee commented on Oct 23, 2026

    @voonyee
    Collaborator

    Can you try running a diagnose from your terminal and share the Diagnostics ID with us?
    See here: https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#diagnose-from-the-terminal

    "
    Create and upload the diagnostics ID. In PowerShell, run:

     For all-user installations
     & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
    
     For per-user installations
     & %LOCALAPPDATA%\Programs\DockerDesktop\resources\com.docker.diagnose.exe" gather -upload
    

    After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051.
    "

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions