From 7de7ee62c5628a3c9e116f14aca63a35d06f5331 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 5 May 2015 13:41:31 -0700 Subject: man: nspawn is used in production these days, admit that Previously, the man page suggested to only use nspawn for testing, building, and debugging things. However, it is nowadays used in production and used as building block for rocket, hence let's just admit that it's pretty much production ready. --- man/systemd-nspawn.xml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'man/systemd-nspawn.xml') diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index cae067bcff..cb96661317 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -84,13 +84,10 @@ kernel modules may not be loaded from within the container. Note that even though these security precautions are taken - systemd-nspawn is not suitable for secure + systemd-nspawn is not suitable for fully secure container setups. Many of the security features may be circumvented and are hence primarily useful to avoid accidental - changes to the host system from the container. The intended use of - this program is debugging and testing as well as building of - packages, distributions and software involved with boot and - systems management. + changes to the host system from the container. In contrast to chroot1 systemd-nspawn -- cgit v1.2.3-54-g00ecf