fix: run registration init container as root #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/init-container-root"
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 forgejo-runner image's default user can't write .runner to the
PVC mount. The manually-deployed runners use runAsUser: 0 for the
init container; match that behavior in the operator.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.15.0 | Safety Check | anthropic | tracking id
r-c62d2a-aa3341This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — The change appropriately fixes a permission issue by running the init container as root to write to the PVC mount, matching existing manual deployment behavior.
Complexity: trivial
Safety Check Review
This change fixes a permission issue where the forgejo-runner image's default user cannot write to the
.runnerfile in the PVC mount. The fix runs the init container as root (RunAsUser: 0) and adds a helper function for the pointer conversion.Key observations:
int64PtrNo security concerns - this is a targeted fix for a legitimate permission issue during initialization.