Comment on Can't access exposed rootful podman container from outside of host device
confusedpuppy@lemmy.dbzer0.com 2 weeks agopodman ps shows the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES daae60bdcc65 docker.io/library/caddy-caddy:latest caddy run --confi... 47 minutes ago Up 47 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:5050->443/tcp, 2019/tcp, 443/udp caddy
netstat -tunpl
shows the following:
Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:5025 0.0.0.0:* LISTEN 3270/sshd: /usr/sbi tcp 0 0 0.0.0.0:5050 0.0.0.0:* LISTEN 7342/conmon tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 7342/conmon tcp 0 0 10.89.0.1:53 0.0.0.0:* LISTEN 7336/aardvark-dns tcp6 0 0 :::5025 :::* LISTEN 3270/sshd: /usr/sbi udp 0 0 10.89.0.1:53 0.0.0.0:* 7336/aardvark-dns
The only difference for the netstat command between Docker and Podman is that Podman show’s entries for aardvark-dns and Docker does not which is something I expect.
InnerScientist@lemmy.world 2 weeks ago
Disable the firewall if you can to check if that’s the issue, then do a tcpdump using root with the port. Do tcpdump inside the container too and compare what you see to the docker environment.
Is caddy-caddy really the correct image?
Try with this command, it’s the minimal setup that works by default (on my machine):
podman run -p 0.0.0.0:5050:80 docker.io/library/caddy:latest