Repository navigation
RLIMIT support - Part 2 - #847
Conversation
|
Documentation preview for this pull request is available at: |
| // | ||
| // Members are prefixed with POSIX_ because they name the seven resource limits | ||
| // specified by POSIX.1. | ||
| enum RlimitResource : ubyte { |
There was a problem hiding this comment.
Is this also covered by config and bundled within the metadata?
There was a problem hiding this comment.
Not in this PR, but the next PR will make this configurable via the regular json config, which is then translated to the flatbuffer schema.
PR #785 has the complete changes, including a feature integration test that checks if rlimits were applied in the started process.
| RecordProperty("Description", "Verify that the forked process exits if setting a limit fails"); | ||
|
|
||
| config_.deployment_config.sandbox.max_cpu_usage = 500; | ||
| config_.deployment_config.sandbox.rlimits = { |
There was a problem hiding this comment.
Testing with ITF in an qemu image would also make sense if the limits are really working
There was a problem hiding this comment.
Yes this is planned for the next PR. All changes are already in #785 but have been broken down into smaller PR for easier review.
MaciejKaszynski
left a comment
There was a problem hiding this comment.
All open comments will be done in the next PR so merging
5a3ebe2
Adds the rlimit values to the internal flatbuffer format of the launch manager.
The values are not yet configurable via json.
This keeps - though ignores - the existing values
max_memory_usageandmax_cpu_usage.There were never really supported and it was always documented in the known limitations:
Next PR will completely remove these parameters.
For a complete example, see #785