6b96087554
Some checks failed
check / gate (push) Failing after 13m33s
The migration step failed with 'could not translate host name postgres'. The Postgres service container was healthy; the job simply could not name it, because service DNS aliases only exist on a per-job network and I had pinned container.network to the flat 'bridge'. That choice was wrong in both directions: it broke service containers AND it was weaker isolation, since every concurrent job shared one bridge and could see its neighbours. A per-job network is stricter and correct — and still has no route to the forge, because these networks live inside the dind daemon, which has no forge attachment at all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
47 lines
1.6 KiB
YAML
47 lines
1.6 KiB
YAML
# act_runner configuration (G7.1).
|
|
#
|
|
# Labels are EXPLICIT and PINNED. `ubuntu-latest` is banned (G7.5): all four
|
|
# windy-registry workflows use it and every single run fails, because a
|
|
# self-hosted runner has no such label unless you invent one. A workflow that
|
|
# names a label nobody provides queues forever and looks like a hung CI system
|
|
# rather than a typo.
|
|
|
|
log:
|
|
level: info
|
|
|
|
runner:
|
|
file: /data/.runner
|
|
capacity: 4 # concurrent jobs; Veron has 24 cores, dind is capped at 12
|
|
timeout: 30m
|
|
shutdown_timeout: 3m
|
|
insecure: false
|
|
fetch_timeout: 5s
|
|
fetch_interval: 2s
|
|
labels:
|
|
- "veron-1:docker://catthehacker/ubuntu:act-22.04"
|
|
- "linux-x64:docker://catthehacker/ubuntu:act-22.04"
|
|
|
|
cache:
|
|
enabled: true
|
|
dir: /data/cache
|
|
|
|
container:
|
|
# Empty = act creates a NETWORK PER JOB and removes it afterwards.
|
|
#
|
|
# This started as `bridge` for isolation, which was a mistake in both
|
|
# directions. It broke service containers — Postgres came up healthy but the
|
|
# job could not resolve the name `postgres`, because service DNS aliases only
|
|
# exist on a per-job network — and it was *weaker* isolation, since every
|
|
# concurrent job shared one flat bridge and could see its neighbours.
|
|
#
|
|
# A per-job network is both correct and stricter. Still no route to the forge:
|
|
# these networks live inside the dind daemon, which has no forge attachment
|
|
# at all.
|
|
network: ""
|
|
privileged: false
|
|
options:
|
|
workdir_parent: /workspace
|
|
valid_volumes: [] # a job cannot bind-mount anything from the daemon host
|
|
docker_host: "-" # do NOT expose the runner's own docker socket to jobs
|
|
force_pull: false
|