2c58234fd9
All checks were successful
CI / Lint, PostgreSQL tests, and package (push) Successful in 54s
The Gitea instance is published on loopback only, and its public name still points at an IPv4 address this host no longer has, so the runner spent seven days failing to fetch tasks with connection refused. Pin the name to the host's LAN address in both places act_runner needs it: extra_hosts for the runner container, and container.options for job and service containers so actions/checkout can clone. nginx already serves a valid certificate for that name on the LAN address, so no DNS, nginx, or ROOT_URL change is required, and the existing runner registration stays valid.
28 lines
661 B
YAML
28 lines
661 B
YAML
log:
|
|
level: info
|
|
|
|
runner:
|
|
file: /data/.runner
|
|
capacity: 1
|
|
timeout: 30m
|
|
shutdown_timeout: 30s
|
|
insecure: false
|
|
env_file: ""
|
|
labels:
|
|
- "python-ci:docker://node:22-bookworm"
|
|
|
|
cache:
|
|
enabled: false
|
|
|
|
container:
|
|
network: ""
|
|
privileged: false
|
|
# Job containers need the same name resolution as the runner itself, otherwise the
|
|
# checkout step clones from an address the job cannot reach. Must match the
|
|
# extra_hosts entry in compose.yaml.
|
|
options: "--add-host=gitea.vandeplanque.com:192.168.1.56"
|
|
valid_volumes: []
|
|
# The daemon uses Docker, but jobs/services do not receive the Docker socket.
|
|
docker_host: "-"
|
|
force_pull: true
|