Note that this will expose procfs and sysfs contents of the host to the guest. Best used with unprivileged containers with additional id mapping. With access to a loop device, mounting a file can circumvent the mknod permission of the devices cgroup, mounting an NFS file system can block the host’s I/O completely and prevent it from rebooting, etc.Īllow nesting. Note that this can have negative effects on the container’s security. This should be a list of file system types as used with the mount command. This is experimental.Īllow mounting file systems of specific types. This requires a kernel with seccomp trap to user space support (5.3 or newer). Essentially, you can choose between running systemd-networkd or docker.Īllow unprivileged containers to use mknod() to add certain device nodes. This is mostly a workaround for systemd-networkd, as it will treat it as a fatal error when some keyctl() operations are denied by the kernel due to lacking permissions. By default unprivileged containers will see this system call as non-existent. This is required to use docker inside a container. Note that interactions between fuse and the freezer cgroup can potentially cause I/O deadlocks.įor unprivileged containers only: Allow the use of the keyctl() system call. This can break networking under newer (>= v245) systemd-network use.Īllow using fuse file systems in a container. Mount /sys in unprivileged containers as rw instead of mixed.
0 kommentar(er)
