fix act-runner: attach job containers to ci network
Some checks failed
CI / lint-test (push) Failing after 50s
Deploy / build (push) Failing after 2m0s
Deploy / scan (push) Has been skipped
Deploy / report-vulns (push) Has been skipped

Job containers spawned by act_runner couldn't resolve 'gitea'
hostname — they were on isolated per-job networks. Setting
GITEA_RUNNER_CONTAINER_NETWORK=ci puts them on the same network
as gitea, enabling git fetch during checkout.
This commit is contained in:
kert
2026-03-23 21:19:40 -04:00
parent f5f62fe65c
commit e690c8c9d8

View File

@@ -227,6 +227,7 @@ services:
- GITEA_RUNNER_REGISTRATION_TOKEN=${ACT_RUNNER_TOKEN}
- GITEA_RUNNER_NAME=homelab-runner
- GITEA_RUNNER_LABELS=ubuntu-latest:docker://catthehacker/ubuntu:act-latest
- GITEA_RUNNER_CONTAINER_NETWORK=ci
volumes:
- ${DOCKER_SOCK:-/run/user/1000/docker.sock}:/var/run/docker.sock
- act_runner_data:/data