for-win icon indicating copy to clipboard operation
for-win copied to clipboard
verified publisher icon docker

wsl integration no longer works - docker socket not found

Open viceice opened this issue 8 months ago • 4 comments

Description

I can no longer access docker from my wsl distribution since today. Confirmed to happen after upgrade to Docker Desktop v4.39.0.

Reproduce

  1. run docker info from wsl

Expected behavior

docker info should be able to talk to the daemon.

docker version

Client:
 Version:           28.0.1
 API version:       1.48
 Go version:        go1.23.6
 Git commit:        068a01e
 Built:             Wed Feb 26 10:41:52 2025
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.39.0 (184744)
 Engine:
  Version:          28.0.1
  API version:      1.48 (minimum version 1.24)
  Go version:       go1.23.6
  Git commit:       bbd0a17
  Built:            Wed Feb 26 10:41:16 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.25
  GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc:
  Version:          1.2.4
  GitCommit:        v1.2.4-0-g6c52b3f
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    28.0.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v0.9.8
    Path:     C:\Users\kriese\.docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.21.1-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.33.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.38
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.5
    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.27
    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.4.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.17.0
    Path:     C:\Users\kriese\.docker\cli-plugins\docker-scout.exe

Server:
 Containers: 5
  Running: 3
  Paused: 0
  Stopped: 2
 Images: 10
 Server Version: 28.0.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc version: v1.2.4-0-g6c52b3f
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.167.4-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 32
 Total Memory: 31.34GiB
 Name: docker-desktop
 ID: 6fbc834f-88a5-46c8-8c88-c7fd5a156122
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

Diagnostics ID

12DBB95A-27C0-4B1E-AB1E-A09D9CA130D7/20250327100827

Additional Info

$ docker info
Client:
 Version:    28.0.1
 Context:    default
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v0.9.4
    Path:     /usr/local/lib/docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.21.1-desktop.2
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.33.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.38
    Path:     /usr/local/lib/docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.5
    Path:     /usr/local/lib/docker/cli-plugins/docker-desktop
  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.27
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /usr/local/lib/docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.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.16.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

$ docker context ls
NAME              DESCRIPTION                               DOCKER ENDPOINT                               ERROR
default *         Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
desktop-linux     Docker Desktop                            npipe:////./pipe/dockerDesktopLinuxEngine
desktop-windows   Docker Desktop                            npipe:////./pipe/dockerDesktopWindowsEngine

viceice avatar Mar 27 '25 10:03 viceice

Confirmed to happen after upgrade to Docker Desktop v4.39.0. Rolling back to v4.38.0 works

viceice avatar Mar 27 '25 10:03 viceice

I have this same issue. Stupidly upgraded back to v4.39.0 and issue starts again.

binduwavell avatar Mar 27 '25 16:03 binduwavell

Same issue, rolling back to v4.38.0 worked for me as well

lobabob avatar Mar 27 '25 19:03 lobabob

Same issue, rolling back to v4.38.0 worked for me as well

I also have this issue.

Every time I try to rollback, within a few hours I'm back on 4.39.0. Talked to our IT team and they don't have anything forcing it to update and I have both update checkboxes unchecked:

Image

brianfreytag avatar Mar 27 '25 19:03 brianfreytag

Think about what will you do when 4.40.0 released? From 4.27 to 4.39, so many times, nearly every release have severe problems. I'm done. Try podman desktop.

hitzhangjie avatar Mar 28 '25 14:03 hitzhangjie

I removed Docker Desktop and installed docker and docker engine inside WSL2. It worked fine afterwards.

  1. Uninstall Docker Desktop
  2. Run this command inside WSL2:
sudo apt update
sudo apt install -y \
  ca-certificates \
  curl \
  gnupg \
  lsb-release

sudo mkdir -p /etc/apt/keyrings

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | \
  sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg

echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] \
  https://download.docker.com/linux/ubuntu noble stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
  1. start docker service: sudo dockerd
  2. test if it works:
docker version
docker run hello-world
  1. I don't know why, I had to run this again in order for docker compose to work
sudo apt update
sudo apt install docker-compose-plugin

rationalthinker1 avatar Apr 04 '25 08:04 rationalthinker1

Has anybody testd v4.40.0?

viceice avatar Apr 07 '25 10:04 viceice

Has anybody testd v4.40.0?

Nope, still an issue on v4.40.0

viceice avatar Apr 07 '25 11:04 viceice 

EB6FEC5B-2454-48F2-BE6A-B735489D72A4/20250407182712

I have a similar issue. Docker Desktop starts normally and works for a while. Then about after an hour, I suddenly lost ability to run any Docker related commands in WSL2 via the command line. Instead I get the error:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

The containers are still running, and in my case I can still access the related web services the containers expose. I just can't seem to control them via WSL2

docker context ls output:

NAME            DESCRIPTION                               DOCKER ENDPOINT                             ERROR
default *       Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
desktop-linux   Docker Desktop                            npipe:////./pipe/dockerDesktopLinuxEngine

RuggMatt avatar Apr 07 '25 18:04 RuggMatt

@viceice thanks for your report. I found something suspicious in the code which handles the /var/run/docker.sock in distros and reverted it. I don't know if it will fix the issue or not, but if you (or anyone else) has the time to give it a try, here's a dev build: https://desktop-stage.docker.com/win/main/amd64/188798/Docker%20Desktop%20Installer.exe

djs55 avatar Apr 08 '25 19:04 djs55 

EB6FEC5B-2454-48F2-BE6A-B735489D72A4/20250409162830

@djs55 I installed the dev build, but now when I go to user the docker command in my WSL2 distro, all I get is the following message:

The command 'docker' could not be found in this WSL 2 distro.
We recommend to activate the WSL integration in Docker Desktop settings.

For details about using Docker Desktop with WSL 2, visit:

https://docs.docker.com/go/wsl2/

I have double-checked that my distro is enabled in Docker Desktop settings.

RuggMatt avatar Apr 09 '25 16:04 RuggMatt

@djs55 still not working. Do you need a new diagnostig id?

$ docker info
Client:
 Version:    28.0.4
 Context:    default
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v0.9.8
    Path:     /home/kriese/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.22.0-desktop.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.34.0-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.38
    Path:     /usr/local/lib/docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.6
    Path:     /usr/local/lib/docker/cli-plugins/docker-desktop
  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.27
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.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.17.0
    Path:     /home/kriese/.docker/cli-plugins/docker-scout
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-feedback" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-feedback: no such file or directory
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

viceice avatar Apr 10 '25 12:04 viceice

@djs55 Also unable to see an improvement with that build. I still am unable to see sockets mount to the WSL2 instance

josef@jSysD docker info
Failed to initialize: protocol not available
 ✘ josef@jSysD docker context ls
NAME              DESCRIPTION                               DOCKER ENDPOINT                             ERROR
default           Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
desktop-linux *   Docker Desktop                            npipe:////./pipe/dockerDesktopLinuxEngine
 josef@jSysD  ls -la /mnt/wsl/docker-desktop/shared-sockets/
total 0
drwxr-xr-x 4 root root  80 Apr 16 17:26 .
drwxr-xr-x 4 root root 100 Apr 16 17:26 ..
drwxr-xr-x 3 root root 460 Apr 16 17:38 guest-services
drwxr-xr-x 2 root root 420 Apr 16 17:38 host-services

JosefSaltz avatar Apr 17 '25 00:04 JosefSaltz

Hit this on 4.40.0, upgrading to 4.41.1 didnt fix it. Rolled back to 4.38 and it works fine. Very frustrating

4.41.1 output:

$ docker info
Client:
 Version:    28.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v1.1.7
    Path:     /usr/local/lib/docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.23.0-desktop.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.35.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.38
    Path:     /usr/local/lib/docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Docker Inc.)
    Version:  v0.1.8
    Path:     /usr/local/lib/docker/cli-plugins/docker-desktop
  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.27
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.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.17.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-scout
WARNING: Plugin "/usr/libexec/docker/cli-plugins/docker-app" is not valid: failed to fetch metadata: fork/exec /usr/libexec/docker/cli-plugins/docker-app: no such file or directory
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-feedback" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-feedback: no such file or directory
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:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

4.38.0 output:

$ docker info
Client:
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.7.3
    Path:     /usr/local/lib/docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1-desktop.2
    Path:     /usr/local/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.4-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.38
    Path:     /usr/local/lib/docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.4
    Path:     /usr/local/lib/docker/cli-plugins/docker-desktop
  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.27
    Path:     /usr/local/lib/docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /usr/local/lib/docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.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.16.1
    Path:     /usr/local/lib/docker/cli-plugins/docker-scout
WARNING: Plugin "/usr/libexec/docker/cli-plugins/docker-app" is not valid: failed to fetch metadata: fork/exec /usr/libexec/docker/cli-plugins/docker-app: no such file or directory
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:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 27.5.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc version: v1.1.12-0-g51d5e946
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.167.4-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 7.759GiB
 Name: docker-desktop
 ID: f8a18310-5e2f-4bf6-bd95-30029038553f
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///var/run/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

marc2982 avatar May 02 '25 22:05 marc2982

it seems this command works, any idea how to make it available to normal users?

$ sudo DOCKER_HOST=unix:///mnt/wsl/docker-desktop/shared-sockets/host-services/docker.proxy.sock docker ps
CONTAINER ID   IMAGE                                        COMMAND                  CREATED        STATUS                         PORTS                    NAMES
d774ca5702b2   bitnami/mariadb:11.4                         "/opt/bitnami/script…"   5 months ago   Up About an hour (healthy)     0.0.0.0:3306->3306/tcp   mariadb
21991fe84be4   bitnami/postgresql:16                        "/opt/bitnami/script…"   5 months ago   Up About an hour               0.0.0.0:5432->5432/tcp   postgresql
6c83a19fd55c   mcr.microsoft.com/mssql/server:2022-latest   "/opt/mssql/bin/perm…"   5 months ago   Up About an hour (unhealthy)   0.0.0.0:1433->1433/tcp   mssql

$ sudo DOCKER_HOST=unix:///mnt/wsl/docker-desktop/shared-sockets/guest-services/docker.proxy.sock docker ps
CONTAINER ID   IMAGE                                        COMMAND                  CREATED        STATUS                         PORTS                    NAMES
d774ca5702b2   bitnami/mariadb:11.4                         "/opt/bitnami/script…"   5 months ago   Up About an hour (healthy)     0.0.0.0:3306->3306/tcp   mariadb
21991fe84be4   bitnami/postgresql:16                        "/opt/bitnami/script…"   5 months ago   Up About an hour               0.0.0.0:5432->5432/tcp   postgresql
6c83a19fd55c   mcr.microsoft.com/mssql/server:2022-latest   "/opt/mssql/bin/perm…"   5 months ago   Up About an hour (unhealthy)   0.0.0.0:1433->1433/tcp   mssql

both socket's are only usable by root 😕

viceice avatar May 13 '25 10:05 viceice

Is this resolved in 2.42.0?

binduwavell avatar Jun 06 '25 17:06 binduwavell

no, still an issue 😥

viceice avatar Jun 06 '25 19:06 viceice

Is this resolved in 2.42.0?

Nope

Here's a diagnostic ID if it helps

EB6FEC5B-2454-48F2-BE6A-B735489D72A4/20250606200141

RuggMatt avatar Jun 06 '25 20:06 RuggMatt

Still an issue on v2.42.1

Diagnostic ID:

12DBB95A-27C0-4B1E-AB1E-A09D9CA130D7/20250630120550

viceice avatar Jun 30 '25 12:06 viceice

4.43.1 has now been released, but I'm still running 4.38.0—and I guess many of us are. Has the issue been resolved for WSL2? Did anyone test it yet?

jldevezas avatar Jul 08 '25 06:07 jldevezas

@jldevezas I was hit by the The command 'docker' could not be found in this WSL 2 distro. issue mentioned by @RuggMatt after upgrading Docker Desktop yesterday. I don't know on which version it was before but I didn't use Docker for a couple of months so likely older than 4.39.0. After fixing the missing symlinks that cause the above error I was presented with the socket not found error which brought me here. Downgrading to 4.38.0 finally fixed this. So, nope, not resolved yet.

So many hours wasted... you can't imagine how relieved I am to have finally have found a solution to this. Why on earth is this not fixed yet?

levrik avatar Jul 08 '25 17:07 levrik

Here's a Diagnostic ID for 4.43.1:

BF14433C-1F67-4BDA-8936-FE4A061ACBE2/20250708171713

levrik avatar Jul 08 '25 17:07 levrik

This remains an issue for me on 4.43.2. Here is a Diagnostics ID:

226362BF-DC15-4450-B80C-A58A8CCE6A23/20250723213117

I'd appreciate it if anyone on 4.38.0 or on a later version with a working WSL integration would share what their /var/run/docker.sock setup (or whatever alternative may be configured by Docker Desktop) looks like.

mcdonnnj avatar Jul 23 '25 21:07 mcdonnnj

Any update on this matter? It's kinda critical, reinstalling latest version doesn't work. Workaround from @viceice works, but it's not a preffered solution.

Leny1337 avatar Aug 07 '25 09:08 Leny1337

Did someone try the latest 4.44.0 release already? There's WSL 2 stability improvements. at the top of the release notes.

levrik avatar Aug 07 '25 13:08 levrik

Just updated to 4.44.0 and ran docker ps on WSL2 and there's still an issue:

❯ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

It's unbelievable that we need to go back to a version that was released on January 2025 for WSL2 to work.

jldevezas avatar Aug 07 '25 22:08 jldevezas

Yeah I can confirm this is still an issue on 4.44.0:

$ docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
$ sudo DOCKER_HOST=unix:///mnt/wsl/docker-desktop/shared-sockets/guest-services/docker.proxy.sock docker images
REPOSITORY   TAG       IMAGE ID   CREATED   SIZE

mcdonnnj avatar Aug 08 '25 14:08 mcdonnnj

@Leny1337 @levrik @mcdonnnj @jldevezas can you please share a diagnostics id?

bsousaa avatar Aug 11 '25 07:08 bsousaa

cc @chelnak

bsousaa avatar Aug 11 '25 07:08 bsousaa

@bsousaa TBH I'm not in the mood of upgrading to the latest release and then having to re-install an older release again to fix my setup, just to capture a new Diagnostics ID while there are many available in this issue already. I did this a few times already and it takes a lot of time. We have Diagnostics IDs up to 4.43.2.

Don't get me wrong. I appreciate someone from Docker finally looking at this issue but shouldn't these many IDs be enough to investigate?

levrik avatar Aug 11 '25 07:08 levrik