From 73990d092c32cad7c9480833652fb35dee93a695 Mon Sep 17 00:00:00 2001 From: litruv Date: Tue, 3 Nov 2026 12:25:13 +1100 Subject: [PATCH] Drop the host-network container option: act_runner ignores --network. (#109) 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. --- .gitea/workflows/tests.yml | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/.gitea/workflows/tests.yml b/.gitea/workflows/tests.yml index af48492..bfd81c4 100644 --- a/.gitea/workflows/tests.yml +++ b/.gitea/workflows/tests.yml @@ -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