SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix capability name, it's CAP_MKNOD not CAP_SYS_MKNOD (#41621)

Browse Source
This commit is contained in:
rusty-snake
2026-04-13 16:41:33 +01:00
committed by GitHub
parent 8383d033cc
commit b40ed2067f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CONTAINER_INTERFACE.md
+2 -2
View File
@@ -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... one Avahi instance on the entire system...
People have been asking to be able to run systemd without `CAP_SYS_ADMIN` and 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 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 off `PrivateTmp=`, `PrivateNetwork=`, `ProtectHome=`, `ProtectSystem=` and
others, because those capabilities are required to implement these options. The others, because those capabilities are required to implement these options. The
services using these settings (which include many of systemd's own) will hence services using these settings (which include many of systemd's own) will hence