This message was deleted.
# generals
sparse-intern-71089
04/20/2023, 2:15 AMThis message was deleted.
c
cuddly-nightfall-71097
04/20/2023, 3:54 AMpodman usually ships a shim package, like podman-docker on Ubuntu.
l
little-cartoon-10569
04/20/2023, 4:01 AMWon't help: the Docker package is using the API, not the CLI. It's connecting to the Docker daemon's port. Which podman doesn't provide (and indeed, that's the entire purpose of podman, to avoid running a root service).
c
cuddly-nightfall-71097
04/20/2023, 4:04 AMIt does.
cuddly-nightfall-71097
04/20/2023, 4:10 AMYou need to start podman (probably as a user service), then either point your tool(s) directly at podman's socket or make a symlink
cuddly-nightfall-71097
04/20/2023, 4:10 AMcuddly-nightfall-71097
04/20/2023, 4:11 AMAnd here an example with docker-compose:
https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md
l
little-cartoon-10569
04/20/2023, 5:21 AMI guess I must have been using a wrong version. I didn't even have a podman machine running, and qemu wasn't installed. But podman was doing everything I needed.. until this point.
Anyway, thanks to your links, I've got podman machine running. However, the socket is still not exposed. I read the socket activation link, but there's nothing in there about Windows/WSL. The startup messages don't look like the ones I see at https://github.com/containers/podman/blob/main/docs/tutorials/podman-for-windows.md, either.
little-cartoon-10569
04/20/2023, 5:21 AMI've installed podman from inside WSL; maybe I need to install the Windows flavour instead?
c
cuddly-nightfall-71097
04/20/2023, 5:29 AMFor socket activation (or running a daemon) - you need to enable / start it manually. Maybe even write own systemd unit (depending on the distro you use)
cuddly-nightfall-71097
04/20/2023, 5:30 AMIf you run windows, did you look into https://podman-desktop.io/ ? My understanding that it runs some WSL distro under the hood...
cuddly-nightfall-71097
04/20/2023, 5:32 AMI personally work with container-related stuff "from within" WSL, i.e. fully remote with almost none integration with windows.
l
little-cartoon-10569
04/20/2023, 8:42 PMI tried that, but was still getting the couldn't-find-the-pipe error. Back at the computer now, will look into it more.
little-cartoon-10569
04/20/2023, 8:43 PMHowever that's what I'd prefer; the podman Desktop and .msi solutions both use podman machine to start up another VM in HyperV, which means I then need to figure out how to mount the from that VM into the VM I'm using. So I'm going to go back to the pure-Linux solution, buoyed by the information that you've got it working successfully.