Repository navigation
fix(openclaw): keep /home/node sticky so 2026.11.6 accepts its temp root - #4953
Merged
Merged
Conversation
Contributor
|
Note 2 resources changed across 2 apps konflate 0.6.6 · rendered |
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 2026.11.6 bump (#4886) crash-looped with
No safe OpenClaw temp root is available: it now refuses any temp root beneath a group-writable ancestor that is not sticky, and/home/node(the PVC root) has to stay g+w for fsGroup.The sticky bit was set by hand on the live volume and the gateway has been stable since. This sets it at every start so a recursive fsGroup chown cannot bring the crash loop back.