# act_runner config — shared by all three runner instances defined
# in ci-runners.compose.yml. Mounted read-only at /etc/runner/config.yaml
# inside each container, selected via the CONFIG_FILE environment variable.
#
# Generated from `act_runner generate-config` and trimmed to the keys we
# actually need to override. Defaults for everything else.
# See: https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml

container:
  # Skip the per-job `docker pull` round-trip when the image is already
  # cached locally. The default (true) re-checks the registry on every
  # job start, adding 10-30s of latency per job for no value once the
  # tag is pinned. Image upgrades happen deliberately on the runner
  # host (see infra/README.md "Updating the runner job images") — not
  # implicitly via :latest.
  force_pull: false

  # Attach every job to the same Docker bridge network as the runner
  # containers themselves. Default behaviour (no value) is for jobs to
  # join Docker's anonymous "bridge" network — different from the
  # compose-defined `apf-portal-act-runners` bridge — which leaves
  # jobs unable to reach the runner-hosted cache server (the IP it
  # binds to and advertises is on the runners' bridge, not the jobs').
  # Sharing the network closes the gap and lets `actions/setup-node`'s
  # `cache: 'pnpm'` work end-to-end. The blast radius is bounded:
  # every container on this network is one of our runner containers,
  # all of which already have full docker-socket access.
  network: apf-portal-act-runners

# Built-in cache server — defaults are good (enabled, listens on a
# pseudo-random port, stores cache under the runner's writable home).
# Documented here only so a future contributor knows where the toggle
# lives if it has to be disabled.
cache:
  enabled: true