iac/ansible/roles/forgejo_runner_interop/templates/docker-compose.yml.j2
Sergei Poljanski d0f6bcf6cf
All checks were successful
deploy / ansible (push) Successful in 4m43s
ansible: run the another-im/interop runner on asxpio-services
The interop project kept a cx23 (claude-test-interop-runner, about
EUR 6/month with its IPv4) only to run its Forgejo runner. Run it here
instead, with the same registration (UUID + token, token in the vault)
and the same three labels, pinned.

Its PR checks are untrusted, so unlike our own runner its jobs get
neither the Docker socket nor host volumes. nix-host, which on the old
host used the host's Nix store as a cache, is a throwaway container for
now; a second, trusted-only registration can bring the cache back.

Rollback: remove the role from site.yaml (or stop the container) and
start the old runner VM again.

Assisted-by: Claude:opus-5-5
2026-11-13 03:47:17 +04:00

12 lines
480 B
Django/Jinja

# Managed by Ansible (role forgejo_runner_interop).
services:
forgejo-runner-interop:
container_name: forgejo-runner-interop
image: code.forgejo.org/forgejo/runner:{{ forgejo_runner_version }}
restart: unless-stopped
user: "0:0" # the runner itself talks to Docker; its jobs do not
command: forgejo-runner daemon --config /config.yaml
volumes:
- ./data:/data
- ./config.yaml:/config.yaml:ro
- /var/run/docker.sock:/var/run/docker.sock