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.4
11–20 of 43 posts
Re: Podman 4.4
#12I 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"
Re: Podman 4.4
#13Earlier 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.
apt install containernetworking-plugins podman-plugins
Re: Podman 4.4
#14Did 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.
If you already have sudo/root access for your user, rootless is just going to cause more problems.
Re: Podman 4.4
#15I 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"
Re: Podman 4.4
#16Did 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
Re: Podman 4.4
#17Re: Podman 4.4
#18I 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"
Re: Podman 4.4
#19Did they sort out rootless networking? I've tried podman twice but simply cannot get networking to work properly when using a docker-compose file.
Re: Podman 4.4
#20Earlier 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