UtilBindVsockAnyPort:286: socket failed 1

[medoni]

Windows Version

Microsoft Windows [Version 10.0.22631.3296]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 20.04.6 LTS

Other Software

• Rancher Desktop v1.13.1
• docker server (moby) v25.0.3
• docker client v25.0.4-rd

Repro Steps

1. Start a new pwsh container

   docker run -v "C:/:/mnt/c/" -it mcr.microsoft.com/powershell:latest
   

2. Inside the container try start cmd.exe

   /mnt/c/Windows/System32/cmd.exe /c set
   

Expected Behavior

Output of cmd.exe or any similar windows host exe

Actual Behavior

<3>WSL (29) ERROR: UtilGetPpid:1293: Failed to parse: /proc/1/stat, content: 1 (pwsh-preview) S 0 1 1 34816 1 1077936384 16289 0 5550 0 127 11 0 0 20 0 19 0 2317128 281159016448 37107 18446744073709551615 94356339937488 94356339979760 140731302623520 0 0 0 0 4096 134431998 0 0 0 17 8 0 0 0 0 0 94356339989568 94356339990872 94356342067200 140731302624847 140731302624860 140731302624860 140731302625250 0
<3>WSL (29) ERROR: UtilBindVsockAnyPort:286: socket failed 1

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• calling exe from ssh on WSL2 will cause UtilAcceptVsock:244: accept4 failed 110 (#8677), similarity score: 0.70

Closed similar issues:

• Problem launching Windows processes from inside WSL2 Docker (#10883), similarity score: 0.72
• Still unable to launch windows processes from WSL when using long environment variables (see #7947 or #6420)) (#9052), similarity score: 0.71
• 0xc0000142 error on powershell (running "cmd.exe /b /c start /b /min powershell.exe" inside WSL) (#9542), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[medoni]

Solved by #10883

[Rajae-Hessani]

Hello medoni, can you give more details on how you resolved this issue

[medoni]

Sry for the late response. --privileged and -v "/run/WSL:/run/WSL" are necessary to run any windows command from inside a docker container.

> docker run --rm `
    --privileged `
    -v "/mnt/c:/mnt/c" `
    -v "/run/WSL:/run/WSL" `
    -it alpine:latest

Inside the alpine, I can execute:

> /mnt/c/Windows/System32/calc.exe

My Environment:

> wsl --version
# WSL version: 2.3.26.0
# Kernel version: 5.15.167.4-1
# WSLg version: 1.0.65
# MSRDC version: 1.2.5620
# Direct3D version: 1.611.1-81528511
# DXCore version: 10.0.26100.1-240331-1435.ge-release
# Windows version: 10.0.22631.4391

> docker info
# Client:
#  Version:    27.2.1-rd
#  Context:    default
#  Debug Mode: false
#  Plugins:
#   buildx: Docker Buildx (Docker Inc.)
#     Version:  v0.17.1
#     Path:     C:\Program Files\Rancher Desktop\resources\resources\win32\docker-cli-plugins\docker-buildx.exe
#   compose: Docker Compose (Docker Inc.)
#     Version:  v2.29.5
#     Path:     C:\Program Files\Rancher Desktop\resources\resources\win32\docker-cli-plugins\docker-compose.exe
# 
# Server:
#  Containers: 83
#   Running: 71
#   Paused: 0
#   Stopped: 12
#  Images: 57
#  Server Version: 26.1.5
#  Storage Driver: overlay2
#   Backing Filesystem: extfs
#   Supports d_type: true
#   Using metacopy: false
#   Native Overlay Diff: true
#   userxattr: false
#  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
#  Swarm: inactive
#  Runtimes: runc io.containerd.runc.v2
#  Default Runtime: runc
#  Init Binary: docker-init
#  containerd version: 3a4de459a68952ffb703bbe7f2290861a75b6b67
#  runc version: 2c9f5602f0ba3d9da1c2596322dfc4e156844890
#  init version:
#  Security Options:
#   seccomp
#    Profile: builtin
#  Kernel Version: 5.15.167.4-microsoft-standard-WSL2
#  Operating System: Rancher Desktop WSL Distribution
#  OSType: linux
#  Architecture: x86_64
#  CPUs: 24
#  Total Memory: 31.35GiB
#  Name: N12
#  ID: db784088-f883-48bb-990b-ebb3b2bf57a4
#  Docker Root Dir: /var/lib/docker
#  Debug Mode: false
#  Experimental: false
#  Insecure Registries:
#   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
#