Open
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.
Summary
This adds sandbox-wide guest rlimits that are applied by
agentdPID 1 during guest startup.Today microsandbox only supports per-exec rlimits. That is too late for bootstrap scripts and long-lived daemons started during guest init, because they inherit PID 1's baseline limits before any per-exec override runs.
What changed
SandboxConfig::rlimitsSandboxBuilder::rlimit(...)andSandboxBuilder::rlimit_range(...)MSB_RLIMITSagentdbefore the rest of init runsWhy this shape
This fixes the real problem for bootstrap daemons and long-lived guest services instead of requiring every process to opt into a higher limit individually.
Validation
cargo test --manifest-path /tmp/msb-baseline/crates/agentd/Cargo.toml --libcargo test --manifest-path /tmp/msb-baseline/crates/microsandbox/Cargo.toml --lib