diff options
| author | Lennart Poettering <lennart@poettering.net> | 2015-05-05 13:41:31 -0700 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2015-05-05 15:07:00 -0700 |
| commit | 7de7ee62c5628a3c9e116f14aca63a35d06f5331 (patch) | |
| tree | 1093f7f6a42c91355678fd926c06fbd77be4b29d | |
| parent | 93c474725c0fb2530f093c106de0bce956544d29 (diff) | |
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.
| -rw-r--r-- | man/systemd-nspawn.xml | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index cae067bcf..cb9666131 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.</para> <para>Note that even though these security precautions are taken - <command>systemd-nspawn</command> is not suitable for secure + <command>systemd-nspawn</command> 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.</para> + changes to the host system from the container.</para> <para>In contrast to <citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>systemd-nspawn</command> |