forgejo-runner: match the live runner and pin the nix image
The role had drifted from what runs on asxpio-services: capacity 4, a bridge network per workflow so service containers start, the Docker socket automounted into jobs, and a nix-latest label backed by a persistent nix-store volume. That volume caused a CI outage on 2026-10-18. nixos/nix:latest moved on, and since the image's /bin/sh and /etc/nix/nix.conf link into /nix/store, the old volume left them dangling. Pin the image through forgejo_runner_nix_version and name the volume after it, so a bump is deliberate and always gets a store seeded from its own image. Assisted-by: Claude:opus-5-5
This commit is contained in:
parent
0af23425f9
commit
a79b110259
3 changed files with 22 additions and 8 deletions
|
|
@ -3,8 +3,14 @@
|
|||
|
||||
# Runner version and settings
|
||||
forgejo_runner_version: "11"
|
||||
forgejo_runner_capacity: 1
|
||||
forgejo_runner_capacity: 4
|
||||
forgejo_runner_timeout: 3h
|
||||
|
||||
# Image behind the nix-latest label. Jobs mount a nix-store volume over
|
||||
# /nix, seeded from this image on first use; the image's /bin/sh and
|
||||
# /etc/nix/nix.conf link into that store, so a volume from another
|
||||
# version breaks them. Bumping this also switches to a fresh volume.
|
||||
forgejo_runner_nix_version: "2.35.3"
|
||||
forgejo_runner_token: "{{ vault_forgejo_runner_token }}"
|
||||
|
||||
# Runner installation path
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue