Automatically bind podman sockets for access by other WSL distributions

[n1hility]

Discussed in #16130

^{Originally posted by derkoe October 12, 2022}
Is it possible to access the podman socket from another WSL distribution?

❯ wsl -l -v
  NAME                      STATE           VERSION
* Fedora                    Running         2
  podman-machine-default    Running         2

❯ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

❯ wsl -d Fedora docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```</div>

[n1hility]

Currently, if you want to do this, manually creating the bind is the recommended approach.

For example, for rootless:

touch /mnt/wsl/podman.sock
sudo mount --bind /var/run/user/1000/podman/podman.sock /mnt/wsl/podman.sock

For rootful:

touch /mnt/wsl/podman.sock
sudo mount --bind /var/run/podman/podman.sock /mnt/wsl/podman.sock

In the future, podman machine start can help by automatically binding into /mnt/wsl in a way that is compatbile with multiple machines, like so:

/mnt/wsl/podman/podman-machine-default-rootless.sock
/mnt/wsl/podman/podman-machine-default-rootful.sock
/mnt/wsl/podman/other-rootless.sock
/mnt/wsl/podman/other-rootful.sock

[gbraad]

Duplicate of

• Allow to automatically set podman connection for other WSL2 instances #15190