whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify example for setting Linux command line

Browse Source
This commit is contained in:
Tim Bannister
2022-01-13 17:43:34 +00:00
parent 66081efd04
commit ef6d83b5dd
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/container-runtimes.md
+6 -2
View File
@@ -76,13 +76,17 @@ If systemd doesn't use cgroup v2 by default, you can configure the system to use
`systemd.unified_cgroup_hierarchy=1` to the kernel command line. `systemd.unified_cgroup_hierarchy=1` to the kernel command line.
```shell ```shell
# dnf install -y grubby && \ # This example is for a Linux OS that uses the DNF package manager
# Your system might use a different method for setting the command line
# that the Linux kernel uses.
sudo dnf install -y grubby && \
sudo grubby \ sudo grubby \
--update-kernel=ALL \ --update-kernel=ALL \
--args="systemd.unified_cgroup_hierarchy=1" --args="systemd.unified_cgroup_hierarchy=1"
``` ```
To apply the configuration, it is necessary to reboot the node. If you change the command line for the kernel, you must reboot the node before your
change takes effect.
There should not be any noticeable difference in the user experience when switching to cgroup v2, unless There should not be any noticeable difference in the user experience when switching to cgroup v2, unless
users are accessing the cgroup file system directly, either on the node or from within the containers. users are accessing the cgroup file system directly, either on the node or from within the containers.