Drop the host-network container option: act_runner ignores --network. (#109)
Tests / unit (pull_request) Successful in 18s
Tests / e2e (pull_request) Successful in 2m56s

Run 928 logged "--network and --net in the options will be ignored", so
NetworkMode stayed the per-job bridge. The fix is a DOCKER-USER exception on
the runner host (pizzabox), which accepts RELATED/ESTABLISHED traffic from
br-f192811a98b7; verified 200 from a bridge container after adding it.
This commit is contained in:
2026-11-03 12:25:13 +11:00
parent e58b87ed3a
commit 73990d092c
+4 -6
View File
@@ -26,12 +26,10 @@ jobs:
# PRs can be trusted with the E2E_PASSWORD secret.
if: github.event.pull_request.head.repo.full_name == github.repository
runs-on: ubuntu-latest
# ruv.wtf is a macvlan interface on a container on the runner host, so the reply to a
# bridge-networked job arrives on that container's bridge and Docker's inter-bridge
# isolation drops it. Host networking keeps the request and reply on one path.
container:
image: docker.io/gitea/runner-images:ubuntu-latest
options: --network=host
# Needs the DOCKER-USER exception on the runner host: ruv.wtf is a macvlan interface on a
# container there, so the reply to a bridge-networked job arrives on that container's bridge
# and Docker's inter-bridge isolation drops it. act_runner ignores --network in
# container.options, so the exception lives on the host.
env:
# Dedicated test account on the homeserver, not a personal one.
E2E_HOMESERVER: ruv.wtf