search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.84k stars 281 forks source link

WSL integration with Debian unexpectedly stopped #14026

Closed Encephala closed 2 months ago

Encephala commented 2 months ago

Description

I upgraded my PC, keeping the storage but changing out motherboard, CPU and RAM. I made sure to enable virtualisation in the new BIOS. Now, when I open Docker Desktop, I get a popup saying "WSL Integratoin with distro 'Debian' unexpectedly stopped. Do you want to restart it?". This error keeps popping up, both when I click to restart the engine or when I click to skip Debian integration.

I was originally using Docker Desktop 4.24, but figuring that an update might fix it, I'm now on 4.29. Besides the error screen now being prettier, nothing changed. A system restart and opening Docker desktop immediately before other programs didn't fix it either.

It could be that there is an issue on my end as this did coincide with the PC upgrade, but because WSL itself works perfectly fine for me, I expect you're better able to figure out what's wrong. If there's something I can do/test, let me know!

Reproduce

  1. Start Docker Desktop
  2. The error occurs
  3. Restarting the engine or manually stopping and reopening causes the same problem.
  4. Restarting my PC doesn't fix it either
  5. In my WSL Debian isntance, docker run hello-world says it fails to communicate with the socket at /var/run/... (naturally)

Expected behavior

The engine starts and integrates properly and I can use it from my Debian installation.

docker version

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.0.0
 API version:       1.45
 Go version:        go1.21.8
 Git commit:        2ae903e
 Built:             Wed Mar 20 15:16:45 2024
 OS/Arch:           linux/amd64
 Context:           default

docker info

Client:
 Version:    26.0.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.13.1-desktop.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.26.1-desktop.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.27
    Path:     /usr/local/lib/docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /usr/local/lib/docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /usr/local/lib/docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /usr/local/lib/docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.6.3
    Path:     /usr/local/lib/docker/cli-plugins/docker-scout
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-scan: no such file or directory

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Diagnostics ID

1985578C-9F70-4848-887D-B77B7D7ADAE1/20240421144643

Additional Info

My .wslconfig only has a setting to change the total memory available to WSL (24 GB). I have an Ubuntu 22.04.3 LTS distribution installed as well, Docker doesn't work in there either.

I guess my current PC specs are probably in the diagnostics, but here they are anyway: My specs are:

Encephala commented 2 months ago

If it helps at all, I have no issues running containers through Podman.

Encephala commented 2 months ago

An uninstall and reinstall fixed the issue. I don't know why I didn't try that, but consider this problem solved.