Access host services with named network

[drewcassidy]

Im setting up forgejo actions with rootless podman as the container engine, but I can never access services running on the host. Forgejo actions always spawns its job containers with a named container, but I've reproduced it with just the cli

if I do
podman network create thingy --driver bridge
and then
podman run --network thingy -it alpine sh

I'm unable to access ANY services running on the host, even ones exposed via the firewall to the outside world. I always get connection refused

what I've tried:

1. setting container.conf [network].pasta_options = ["-T", "8000"] where 8000 is the port I'm using to test this behavior
2. running with -p 8000:8000. it doesnt make a difference
3. accessing the host via host.container.internal or 10.89.0.1 (or whatever the configured gateway is)

I think part of my difficulty understanding this is that the options for podman run --network are completely different from anything in podman network create and I'm not sure how to map from one to the other. It seems I want a named network that uses pasta to get this to work, but I dont know how to create one if that is even possible.

[drewcassidy]

aha, its host.containers.internal 😸