Live data from Hacker News

Podman 4.4

github.com

11–20 of 43 posts

Re: Podman 4.4

#11

Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.

I too have issues with this, but mainly trying to run protected ports (port 53 for DNS with PiHole) as rootless Podman -- it just did not work. Went back to docker and have not had an issue since.

Re: Podman 4.4

#12
post #6

I hope more open source projects support it. Most repos I check out still have only docker specific commands… Even though most things are similar, the differences in e.g networking (for example host.docker.internal vs host.containers.internal) create lots of Issues for me

You may be able to symlink podman to /usr/bin/docker and things should "Just Work"

That was the smartest decision they made other than the product itself

Re: Podman 4.4

#13
post #8

Earlier quoted context omitted.

What was wrong with it?

It is very difficult getting containers that aren’t in a pod together to be able to talk to each other, with rootless pods, and without just host-binding everything. None of the normal hostname conveniences are in place, and if it’s possible to do it isn’t default and probably needed much more underlying knowledge than I had when I tried.

Had the same issue, the containers did not resolve each other by hostname. This fixed it (run on the host):

apt install containernetworking-plugins podman-plugins

Re: Podman 4.4

#14

Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.

I too have issues with this, but mainly trying to run protected ports (port 53 for DNS with PiHole) as rootless Podman -- it just did not work. Went back to docker and have not had an issue since.

Just don't use rootless. You can still do user namespace containers (the real benefit to rootless, IMO) as a root user. I predict we will find all sorts of fun, niche security bugs that were made to get rootless containers working, especially networking--linux really doesn't like unprivileged changes to the networking stack.

If you already have sudo/root access for your user, rootless is just going to cause more problems.

Re: Podman 4.4

#15
post #6

I hope more open source projects support it. Most repos I check out still have only docker specific commands… Even though most things are similar, the differences in e.g networking (for example host.docker.internal vs host.containers.internal) create lots of Issues for me

You may be able to symlink podman to /usr/bin/docker and things should "Just Work"

[deleted]

Re: Podman 4.4

#16
post #7

Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.

I haven’t had issues with rootless networking but I run pretty simple apps. I gave up on podman-compose though and run individual commands to create podman objects. Once rootless containers are in the same pod you can access other containers in the same pod over localhost

Podman has a Docker-compatible service API, so you can use it via docker-compose.

Re: Podman 4.4

#17
How do we encourage other repos like Ubuntu to update to this version? I'd love to have some Ubuntu like distro that has faster / rolling updates for WSL and some VMs. Even the next version of Ubuntu is still stuck on version 3.4...

Re: Podman 4.4

#18
post #6

I hope more open source projects support it. Most repos I check out still have only docker specific commands… Even though most things are similar, the differences in e.g networking (for example host.docker.internal vs host.containers.internal) create lots of Issues for me

You may be able to symlink podman to /usr/bin/docker and things should "Just Work"

I got my simple docker files working with podman but my more advanced ones didn't. This was about 8 months ago. After running podman for about 2-3 weeks on my dev machine, I went back to docker.

Re: Podman 4.4

#19

Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.

Podman 4.0 brought a new network stack for rootless called Netavark. Works nicely for me.

Re: Podman 4.4

#20
post #8

Earlier quoted context omitted.

It is very difficult getting containers that aren’t in a pod together to be able to talk to each other, with rootless pods, and without just host-binding everything. None of the normal hostname conveniences are in place, and if it’s possible to do it isn’t default and probably needed much more underlying knowledge than I had when I tried.

Had the same issue, the containers did not resolve each other by hostname. This fixed it (run on the host): apt install containernetworking-plugins podman-plugins

That's not needed/used since Podman 4, where the networking stack was rewritten; one of the features of the new "netavark" stack is that it has DNS resolution for containers within a network by default, no plugin needed.
Post reply on HN