Repository navigation
fix: allow non-root canary runtime files on its emptyDir - #4
Closed
r33drichards wants to merge 1 commit into
Closed
r33drichards wants to merge 1 commit into
r33drichards wants to merge 1 commit into
Conversation
Author
|
Superseded by the user-requested native Docker/ECR pivot after the WASM owner stood down. This unapplied fsGroup-only canary change is not being merged. Preserve the branch and public repository for audit; runtime removal is coordinated separately through cloud GitOps. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Source preflight identified that InspIRCd::WritePID opens /irc/inspircd.pid and exits on failure, while the canary runs UID/GID1000 with an emptyDir and no fsGroup. Add only pod fsGroup1000 so the existing runtime emptyDir is writable by that user. Preserve non-root UID/GID, read-only rootfs, dropped capabilities, seccomp, localhost-only bind, immutable image and no token. This is a source-identified startup risk, not yet an observed live error because sandbox creation is separately blocked by shim options. No privileges/hostPath/RBAC/public ingress. Server dry-run and diff check pass. Cloud source remains pinned to previous commit until exact-head CI/review plus separate reviewed pin update; current HTTP healthy.