Three fixes for runner reliability:
1. Fix service startup order (install_runner.yml)
- Move service.yml include BEFORE register.yml
- Previously, register.yml tried to start gitea-runner.service
before service.yml created the systemd unit file, causing
"Unit gitea-runner.service not found" on first install
- This only failed when registration actually happened (new runner);
on idempotent re-runs registration was skipped so the bug was masked
2. Restart runner after (re-)registration (register.yml)
- Add "Restart runner service after (re-)registration" task
- When a runner is re-registered (force-reregister or auto-recovery),
the service must be restarted to pick up the new .runner file
- The old premature start task was already removed; this adds it back
in the correct position (after service.yml has created the unit)
3. Docker daemon restart override (rootless_docker.yml)
- Add Restart=always, RestartSec=5, StartLimitIntervalSec=300,
StartLimitBurst=10 to both Docker service override blocks
- Upstream dockerd-rootless-setuptool.sh defaults to
StartLimitBurst=3 in 60s — too aggressive for OOM-prone hosts
- If Docker crashes 3 times in a minute, it stops restarting
permanently, taking the runner down with it
- New settings allow 10 restarts in 5 minutes, matching the
runner service's own restart policy
Note: Auto-recovery (--auto-recover-token) already exists in the CLI
and healthcheck script but defaults to disabled. Operators should pass
--auto-recover-token <token> during grm install to enable automatic
re-registration when runners become unregistered.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
