apps(forgejo): clear stale dind pid on start so runner restarts self-heal #14
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/dind-stale-pid"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
siriussec was rebooted and the amd64 Forgejo runner came back in
CrashLoopBackOff:dind-runis anemptyDirmounted at/var/run. A reboot restarts the dindcontainer inside the same pod, so the emptyDir survives and still holds the
dead daemon's
docker.pid. In the fresh container PID 7 is some other process,so dockerd's liveness check fails and it refuses to start — permanently, until
someone deletes the pod.
This affects
runner-arm64.yamlidentically; it just hadn't rebooted into thebad state yet.
Change
Clear the stale runtime state immediately before starting dockerd, in both
runner manifests:
The container is fresh at that point, so there is no live daemon to disturb —
this only removes leftovers from the previous container instance.
Verification
yaml.safe_load_all): amd64 -> PVC + Deployment, arm64 -> Deployment.dindcommand passessh -n.pod (state lives on the
forgejo-runner-amd64PVC, nothing lost):No cluster-side manifest change was made outside this PR; the live fix was the
pod delete above.