mirror of
https://github.com/systemd/systemd.git
synced 2026-06-24 08:47:49 +00:00
docs: fix capability name, it's CAP_MKNOD not CAP_SYS_MKNOD (#41621)
This commit is contained in:
@@ -403,9 +403,9 @@ its user to 2 (to effectively disallow `fork()`ing) you cannot run more than
|
||||
one Avahi instance on the entire system...
|
||||
|
||||
People have been asking to be able to run systemd without `CAP_SYS_ADMIN` and
|
||||
`CAP_SYS_MKNOD` in the container. This is now supported to some level in
|
||||
`CAP_MKNOD` in the container. This is now supported to some level in
|
||||
systemd, but we recommend against it (see above). If `CAP_SYS_ADMIN` and
|
||||
`CAP_SYS_MKNOD` are missing from the container systemd will now gracefully turn
|
||||
`CAP_MKNOD` are missing from the container systemd will now gracefully turn
|
||||
off `PrivateTmp=`, `PrivateNetwork=`, `ProtectHome=`, `ProtectSystem=` and
|
||||
others, because those capabilities are required to implement these options. The
|
||||
services using these settings (which include many of systemd's own) will hence
|
||||
|
||||
Reference in New Issue
Block a user