Accessing exposed ports from containers
14 Mar
2024
14 Mar
'24
5:42 p.m.
Hi, I'm trying to run a gitea runner with an exposed port where a caching server listens. Dynamically spawned containers want to connect on <hostip>:<exposedport> and get a timeout. The port is exposed in the common way (mapping <extport>:<intport> in docker-compose.yml) and accessible on the external IP from outside. Host-OS is Arch, networking via netavark, default bridge setup and podman 4.9.3. I'm wondering why the containers can't connect to the exposed port on the host while external connections are possible. Regards Bjoern
938
Age (days ago)
938
Last active (days ago)
1 comments
1 participants
participants (1)
-
Bjoern Franke