fix(backend): make .runner group-writable for the daemon #46
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/runner-dot-runner-group-writable"
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?
The register init container runs as root and writes .runner to the PVC as
0:0 mode 644, while the daemon container runs as the runner image's default
user (uid 1000, gid 0). Some forgejo-runner releases (e.g. v12.6.4) re-save
.runner when the daemon boots; against a non-group-writable file that fails
with "open .runner: permission denied" and the daemon crash-loops. Other
releases (e.g. v12.7.3) only read it, so whether a pool works depends on
which patch the floating :12 tag happened to pull -- a latent, node-
dependent trap.
Since the daemon shares the root group (gid 0), make the data dir and
.runner group-writable from the register script. It runs on every start
(both the fresh-register and already-registered paths) so a .runner left
non-group-writable by an older operator is repaired in place. This lets the
runner image keep floating on :12 safely.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Automated review by pr-reviewer v0.31.0 | Safety Check | Mistral Small | tracking id
r-5834ed-27fef5This is an AI-generated review and may contain mistakes.
Status: ⚠️ Unavailable
Review unavailable — the inference service isn't reachable right now. This isn't a problem with your PR. Tracking id
r-5834ed-27fef5.Comment
@pr-reviewer-bot retryonce it's back.