4 ms·
That's documentation for RHEL 6 which is now 12 years old. It pertains to cgroups v1 which was horribly complex. It was replaced by cgroups v2 which is much sim
by yrro 4y ago
That's documentation for RHEL 6 which is now 12 years old. It pertains to cgroups v1 which was horribly complex. It was replaced by cgroups v2 which is much simpler; there's now a single hierarchy of cgroups.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/setting-limits-for-applications_monitoring-and-managing-system-status-and-performance https://access.redhat.com/documentation/en-us/red_hat_enterp...
That said I don't remember having to learn all that much about cgroups when I last looked at lxc...
- amelius 4y agoThanks! Well, I started looking into it because there were all these mounted filesystems that I couldn't unmount, even as root. I guess I will have to look into namespaces also.
- yrro 4y agoYeah, it's pretty much an implementation detail - the thing running your containers likely exposes knobs like 'memory limit' and 'cpu limit' and under the hood it takes care of manipulating the files within the mounted cgroup filesystem. You'll be pleased that at least with cgroups v2 there's only a single /sys/fs/cgroup instead of half a dozen filesystems mounted underneath that path. :)