fix: preserve Git initialization after Substrate privilege drop - #56
Merged
Conversation
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
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.
The execution bootstrap starts as root before dropping to UID65532. Container runtimes inject HOME=/root, so libgit2 refuses new workspace initialization when the daemon later tries to stat /root/.gitconfig. Existing workspace reads and empty-workspace terminal checks do not exercise that path.
Set HOME=/nonexistent for execution-enabled Substrate pods, excluding the inaccessible root home without adding a writable home or authority. Both ordinary and quota execution renders assert the setting. Chart0.8.32 is the only publication output; application/runtime images are unchanged.
Validation: the native libgit2 probe reproduces the precise root-home error and passes with the absent home. Chart lint, version consistency and the complete rollout check pass, including8 real volume initializer executions. Hosted acceptance identified the failure and will be repeated after the chart-only release. AEP validation reports valid with existing advisories.