Bug in podman installation on WSL2 distribution because RemoteSocket: path: /mnt/wslg/runtime-dir/podman/podman.sock is not available. #16861
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
After podman installation on WSL2 distribution the remote socket is set as /mnt/wslg/runtime-dir/podman/podman.sock
Steps to reproduce the issue:
Install Podman Desktop on Windows and
podman machine init
thepodman-machine-default
machine on WSL2.Check the machine is running
podman machine ssh
Run
podman info
, seems ok, test containers works as expectedOutput:
Output:
podman --remote info
-->unable to connect to Podman socket
errorError output:
$ ls -la /mnt/wslg/runtime-dir/podman/podman.sock ls: /mnt/wslg/runtime-dir/podman/podman.sock: No such file or directory $ ls -la /mnt/wslg/runtime-dir total 0 drwx------ 6 agc00001 agcorp.i 160 Dec 16 10:34 . drwxrwxrwt 7 root root 300 Dec 16 10:34 .. drwx------ 6 agc00001 agcorp.i 120 Dec 16 10:34 containers drwx------ 3 agc00001 agcorp.i 60 Dec 16 10:34 dbus-1 drwx-----T 3 agc00001 agcorp.i 60 Dec 16 10:34 libpod drwx------ 2 agc00001 agcorp.i 80 Dec 16 10:34 pulse srwxrwxrwx 1 agc00001 agcorp.i 0 Dec 16 10:34 wayland-0 -rw-rw---- 1 agc00001 agcorp.i 0 Dec 16 10:34 wayland-0.lock
Describe the results you received:
Error: Unable to connect to Podman socket
Describe the results you expected:
podman-machine-default
machine on WSL2Additional information you deem important (e.g. issue happens only occasionally):
This issue happens on a fresh install of the machine and client.
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Podman was build on docker image which is imported as WSL2 distribution using EasyWSL tool.
Following is the Dockerfile used to build the image:
Output:
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: