I have a problem where #podman containers' ports are published in such a way that they are accessible from localhost but not the LAN. Looks like they listen on 127.0.0.1 rather than, say, 192.168.1.1. So from another machine in the same network, say 192.168.1.2 I can't access them.
Does that ring a bell? #followerpower #routing #network #issues
@cweickhmann Can you share the command line you used to create / run the container ?
@Coolgeek It happens with any container, e.g. `sudo podman run -p 10080:80 docker.Io/library/httpd`.
I don't see a difference between rootful and -less either.
@cweickhmann That's weird. Did you check for firewall ? What is the output of "ss -nlp" ?
@Coolgeek Weird indeed. There's no firewall. I cannot produce the actual output of `ss -npl` at the moment, but it claims the ports are bound to 0.0.0.0:10080 by conmon.
I suspect an issue with my installation, as the podman packages come from the testing branch of Debian bookworm for ARM while the host is actually an Armbian 26 (bookworm based).
I also ran into an issue where I could for the love of the podgod not change the graphRoot directory.
Yeah, it's really weird. Since your responses show that I'm not totally insane (thanks a lot! ^^) I think I'll make the effort to move the system out of that weird state into a more recent non-frankensteinian Armbian state. I just read that there's a Debian 13/Trixie based image now, so that should lead somewhere.
@cweickhmann nice ! I'm glad it works now ! 🎆
@Coolgeek Un-frankensteined the system (upgraded to Trixie).
Aaaand: it works!
Thanks for the feedback!