8245ebfb07
The forgejo runner lives inside the forgejo-runner Incus container with the host's incus socket mounted in. From inside, the operator-side SSH alias \`srv-102v\` doesn't resolve — Ansible's first task tried to ssh and bailed with UNREACHABLE. Switching the incus host entry to \`ansible_connection: local\` is sound because every incus_hosts task only invokes the \`incus\` CLI, which talks to the daemon over the mounted socket. No SSH-into-host needed. ZFS snapshot/prune plays still need real ZFS on the host, which the runner doesn't have — wrapped them in \`command -v zfs\` so they no-op on the runner instead of erroring. The snapshot is a safety net, not a correctness gate; for full safety run deploy_data.yml from the operator laptop with --vault-password-file. Same change applied to inventory/prod.yml. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ansible | ||
| coturn | ||
| nginx-rtmp | ||
| docker-compose.lab.yml | ||