blumeops/containers/forgejo-runner/config.yaml
Erich Blume 008533491f
Some checks failed
Build Container / build (push) Failing after 41s
Add containerized forgejo-runner for Phase 1 ratcheting
Part of the runner ratcheting plan to migrate from host-mode to k8s runners.

- Debian-based image with forgejo-runner and Docker CLI
- Mounts Docker socket for container builds
- Auto-registers on first start
- Host networking for access to *.ops.eblu.me services

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 17:21:29 -08:00

25 lines
646 B
YAML

# Forgejo Runner configuration
# See: https://forgejo.org/docs/latest/admin/actions/#configuration
log:
level: info
runner:
file: /data/.runner
capacity: 2
timeout: 3h
# Fetch task interval
fetch_timeout: 5s
fetch_interval: 2s
container:
# Use host network so containers can reach services on the host
# (e.g., registry.ops.eblu.me resolves to host's Tailscale IP)
network: host
# Don't use privileged mode by default
privileged: false
# Mount docker socket for container builds
options: -v /var/run/docker.sock:/var/run/docker.sock
# Valid volumes that can be mounted
valid_volumes:
- /var/run/docker.sock