Docker Desktop 4.33.0 does not start without admin

[theBNT]

Description

Hi,

just installed the Docker Desktop 4.33.0 version due to the CVE-2024–41110 but it seems that it cant startup properly on a Windows 11 system without local admin permissions.

On first start, it prompts to enter admin credentials, which i have to answer with No (or use the upper right X),

then the error

wsl update failed: updating wsl: elevated update failed: the operating system denied access to the specified file

is shown.

When manually checking the wsl version via powershell

PS > wsl --version
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3880
PS > wsl --update
Checking for updates.
The most recent version of Windows Subsystem for Linux is already installed.
PS >

it seems there is no new version to update to.

Sent in diagnostics with ID: F4DDD488-70F3-4DF9-85A5-14E794571B41/20240802124231

Reproduce

1. Have docker desktop 4.32.0 installed
2. Update to 4.33.0
3. Start Docker (e.g. via start menu)

Expected behavior

docker starts up correctly or specifies steps to fix the problem, without local admin permissions.

docker version

Client:
 Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:57:57 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux
error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/version": EOF

docker info

Client:
 Version:    27.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.11.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/info": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

F4DDD488-70F3-4DF9-85A5-14E794571B41/20240802124231

Additional Info

No response

[glen-84]

Related: #13806.

[theBNT]

Thanks @glen-84 - looks like also 4.33.1 does not fix it unfortunately. there is also a thread in #13868 so it might be related as well

[andrea-reale]

Hey all, I have shared a development build that should avoid this loop of "WSL Update required" prompts here. Feel free to try that out and report any feedback!

(Please, also note that custom WSL2 kernels are not officially supported in Docker Desktop - some of the diagnostics shared in this and other threads point to that as a common source of the problem)

[theBNT]

ill close this issue since there are enough duplicate threads and it seems that according to the first reports, your fix is working for them! thanks!