Error Windows wsl: All pipe instances are busy.

[hupling]

windows 11 with wsl behind vpn

$ wsl --version
WSL-Version: 2.4.12.0
Kernelversion: 5.15.167.4-1
WSLg-Version: 1.0.65
MSRDC-Version: 1.2.5716
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.26100.8037

$ podman --version
podman version 5.8.0

I am getting the following error with the version v5.7.1 . Version v5.7.0 works perfect.

podman machine start
Starting machine "podman-machine-default"
Starting user-mode networking...

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

        podman machine set --rootful

API forwarding for Docker API clients is not available due to the following startup failures.
        CreateFile \\.\pipe\docker_engine: Alle Pipeinstanzen sind ausgelastet.

Podman clients are still able to connect.
Error: machine did not transition into running state: ssh error: machine not in running state 

[Luap99]

Sorry for not replying earlier.

Does this still happen with podman 5.8 or 6.0 images and clients? Note the major and minor version (x.y) should be matched between image and client.

In general for podman issues like that it is best to report these as bugs against the podman repo, we have a lot more people triaging bugs there. Even if you can be sure it is a problem with the image version we can always move it later once we confirmed it.

The pipe error AFAIK is not fatal and can be ignored if you do not need it. machine did not transition into running state: ssh error: machine not in running state is the fatal error and means ssh is not working so we cannot connect to the machine. In case of wsl it should be possible to manually start the wsl machine and enter it with wsl and then check the ssh logs to see why ssh failed.

cc @l0rd

[l0rd]

User-mode networking was broken in 5.8 podman-container-tools/podman#28609 and got fixed in 5.8.3. Also, the version of WSL is quite old (try wsl --update if possible).

The pipe busy message shouldn't be an issue per se (Podman can still be used without problem) but may indicate something wrong (who created \.\pipe\docker_engine? is there a process still listening?).