Files
apf_portal/infra/ci-runners.compose.yml
T
Julien Gautier 4934fc29da
CI / commits (pull_request) Successful in 1m22s
CI / check (pull_request) Successful in 1m29s
CI / scan (pull_request) Failing after 1m32s
CI / a11y (pull_request) Successful in 1m35s
CI / perf (pull_request) Successful in 2m55s
chore(infra): pin act_runner image pull policy
`act_runner`'s default `container.force_pull: true` re-issues a
`docker pull` at the start of every job, adding 10-30 s of registry
round-trip per job even when every layer is already locally cached.
The job images are already pinned to specific tags (catthehacker
ubuntu :act-22.04 + :full-22.04), so the implicit pull is both pure
overhead and contradictory with the deliberate-upgrade policy
ADR-0015 spells out for the runner image itself.

Mount a shared `infra/runner-config.yaml` into all three runners
with `force_pull: false`, point each runner at it via the
`CONFIG_FILE` env var, and document the pre-pull procedure (one-shot
`docker pull` on the runner host, plus the upgrade playbook) in
infra/README.md "Job image pinning and pre-pull".

The pre-pull is also folded into the "First-time registration"
walkthrough so a fresh setup is correct end-to-end.
2026-05-04 15:45:18 +02:00

94 lines
4.3 KiB
YAML

# Self-hosted Gitea Actions runners — per ADR-0015 §"Runners".
#
# Three act_runner instances registered with the project's Gitea
# organisation, labelled self-hosted + on-prem (the labels referenced
# by every job in .gitea/workflows/*).
#
# First-time registration, scaling, image pinning, and security notes
# are documented in infra/README.md.
name: apf-portal-ci-runners
services:
runner-1:
image: gitea/act_runner:0.2.13
container_name: apf-portal-runner-1
restart: unless-stopped
environment:
GITEA_INSTANCE_URL: ${GITEA_INSTANCE_URL:?GITEA_INSTANCE_URL must be set in infra/.env}
GITEA_RUNNER_REGISTRATION_TOKEN: ${GITEA_RUNNER_REGISTRATION_TOKEN:-}
GITEA_RUNNER_NAME: apf-portal-runner-1
# Labels are formatted as <label>:docker://<image>. Without the
# docker:// suffix, act_runner uses a minimal default image with no
# Node, breaking any JavaScript action (actions/checkout etc.).
# catthehacker/ubuntu:act-22.04 is the de facto standard for
# act-compatible runners — bundles Node, Python, git, common build
# tools, and the Docker CLI.
GITEA_RUNNER_LABELS: self-hosted:docker://catthehacker/ubuntu:act-22.04,on-prem:docker://catthehacker/ubuntu:act-22.04
# Path of the shared act_runner config file inside the container,
# mounted read-only via volumes below (see infra/runner-config.yaml).
CONFIG_FILE: /etc/runner/config.yaml
volumes:
# Docker socket — see security note in infra/README.md.
- /var/run/docker.sock:/var/run/docker.sock
# Persistent state: runner credentials live here after first registration.
- ./data/runner-1:/data
# Shared act_runner configuration — see infra/runner-config.yaml.
- ./runner-config.yaml:/etc/runner/config.yaml:ro
networks:
- act-runners
runner-2:
image: gitea/act_runner:0.2.13
container_name: apf-portal-runner-2
restart: unless-stopped
environment:
GITEA_INSTANCE_URL: ${GITEA_INSTANCE_URL:?GITEA_INSTANCE_URL must be set in infra/.env}
GITEA_RUNNER_REGISTRATION_TOKEN: ${GITEA_RUNNER_REGISTRATION_TOKEN:-}
GITEA_RUNNER_NAME: apf-portal-runner-2
# Labels are formatted as <label>:docker://<image>. Without the
# docker:// suffix, act_runner uses a minimal default image with no
# Node, breaking any JavaScript action (actions/checkout etc.).
# catthehacker/ubuntu:act-22.04 is the de facto standard for
# act-compatible runners — bundles Node, Python, git, common build
# tools, and the Docker CLI.
GITEA_RUNNER_LABELS: self-hosted:docker://catthehacker/ubuntu:act-22.04,on-prem:docker://catthehacker/ubuntu:act-22.04
# Path of the shared act_runner config file inside the container,
# mounted read-only via volumes below (see infra/runner-config.yaml).
CONFIG_FILE: /etc/runner/config.yaml
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data/runner-2:/data
- ./runner-config.yaml:/etc/runner/config.yaml:ro
networks:
- act-runners
runner-3:
image: gitea/act_runner:0.2.13
container_name: apf-portal-runner-3
restart: unless-stopped
environment:
GITEA_INSTANCE_URL: ${GITEA_INSTANCE_URL:?GITEA_INSTANCE_URL must be set in infra/.env}
GITEA_RUNNER_REGISTRATION_TOKEN: ${GITEA_RUNNER_REGISTRATION_TOKEN:-}
GITEA_RUNNER_NAME: apf-portal-runner-3
# Labels are formatted as <label>:docker://<image>. Without the
# docker:// suffix, act_runner uses a minimal default image with no
# Node, breaking any JavaScript action (actions/checkout etc.).
# catthehacker/ubuntu:act-22.04 is the de facto standard for
# act-compatible runners — bundles Node, Python, git, common build
# tools, and the Docker CLI.
GITEA_RUNNER_LABELS: self-hosted:docker://catthehacker/ubuntu:act-22.04,on-prem:docker://catthehacker/ubuntu:act-22.04
# Path of the shared act_runner config file inside the container,
# mounted read-only via volumes below (see infra/runner-config.yaml).
CONFIG_FILE: /etc/runner/config.yaml
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data/runner-3:/data
- ./runner-config.yaml:/etc/runner/config.yaml:ro
networks:
- act-runners
networks:
act-runners:
name: apf-portal-act-runners