Setup cgroup.subtree_control controllers when necessary in cgroupsv2 #208
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.
This commit adds extra setup when cgroupsv2 is enabled. In particular, we make sure that the root cgroup (whatever
cgroupv2_mount
is set to) has setup cgroup.subtree_control with the controllers we need.If the necessary controller are not listed, we have to move all processes out of the root cgroup before we can change this (the 'no internal processes' rule: https://unix.stackexchange.com/a/713343). Currently this handles the case where the nsjail process is the only process in the cgroup. It seems like this would be relatively rare, but since nsjail is frequently the root process in a Docker container (e.g. for hosting CTF challenges), I think this case is common enough to make it worth implementing.
This also adds
--detect_cgroupv2
, which will attempt to detect whether--cgroupv2_mount
is a valid cgroupv2 mount, and will setuse_cgroupv2
accordingly. This is useful in containerized environments where you may not know the configuration ahead of time.References:
https://github.com/redpwn/jail/blob/master/internal/cgroup/cgroup2.go
See #196