docs: fix wrong capability name

It's CAP_SYS_BOOT, not CAP_BOOT.

Signed-off-by: Florian Klink <flokli@flokli.de>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This commit is contained in:
Florian Klink 2023-07-13 15:59:27 +03:00 committed by Andrey Smirnov
parent 59d7d9344b
commit b84277d7dc
No known key found for this signature in database
GPG Key ID: 7B26396447AB6DFD
2 changed files with 2 additions and 2 deletions

View File

@ -9,7 +9,7 @@ Linux defines a set of [process capabilities](https://man7.org/linux/man-pages/m
Talos Linux for security reasons restricts any process from gaining the following capabilities:
* `CAP_SYS_MODULE` (loading kernel modules)
* `CAP_BOOT` (rebooting the system)
* `CAP_SYS_BOOT` (rebooting the system)
This means that any process including privileged Kubernetes pods will not be able to get these capabilities.

View File

@ -9,7 +9,7 @@ Linux defines a set of [process capabilities](https://man7.org/linux/man-pages/m
Talos Linux for security reasons restricts any process from gaining the following capabilities:
* `CAP_SYS_MODULE` (loading kernel modules)
* `CAP_BOOT` (rebooting the system)
* `CAP_SYS_BOOT` (rebooting the system)
This means that any process including privileged Kubernetes pods will not be able to get these capabilities.