Files
nomad/website/content/partials/install/cgroup-controllers.mdx
Aimee Ukasick 021692eccf docs: refactor CNI plugin content (#23707)
- Pulled common content from multiple pages into new partials
- Refactored install/index to be OS-based so I could add linux-distro-based instructions to install-consul-cni-plugins.mdx partial. The tab groups on the install/index page do match and change focus as expected.
- Moved CNI overview-type content to networking/index
- Refactored networking/cni to include install CNI plugins and configuration content (from install/index).
- Moved CNI plugins explanation in bridge mode configuration section into bullet points. They had been #### headings, which aren't rendered in the R page TOC. I tried to simplify and format the bullet point content to be easier to scan.

Ref: https://hashicorp.atlassian.net/browse/CE-661
Fixes: https://github.com/hashicorp/nomad/issues/23229
Fixes: https://github.com/hashicorp/nomad/issues/23583
2024-08-06 14:47:46 -04:00

23 lines
914 B
Plaintext

On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
Nomad supports both [cgroups
v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
legacy [cgroups
v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
When Nomad clients start, they determine the available cgroup controllers and
include the attribute `os.cgroups.version` in their fingerprint.
On cgroups v2, you can run the following command to verify that you have all
required controllers.
```shell-session
$ cat /sys/fs/cgroup/cgroup.controllers
cpuset cpu io memory pids
```
On legacy cgroups v1, this same list of required controllers appears as a series
of sub-directories under the directory `/sys/fs/cgroup`.
Refer to the [cgroup controller
requirements](/nomad/docs/install/production/requirements#cgroup-controllers)
for more details and to enable missing cgroups.