From 77b6e19458f37cfde127ec6aa9494c0ac45ad890 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 10 May 2013 00:14:12 +0200 Subject: audit: since audit is apparently never going to be fixed for containers tell the user what's going on Let's try to be helpful to the user and give him a hint what he can do to make nspawn work with normal OS containers. https://bugzilla.redhat.com/show_bug.cgi?id=893751 --- man/systemd-nspawn.xml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) (limited to 'man/systemd-nspawn.xml') diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index d9fb899895..1bc61e83a7 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -142,16 +142,19 @@ might be necessary to add this file to the container tree manually if the OS of the container is too old to contain this file out-of-the-box. + + + + Incompatibility with Auditing Note that the kernel auditing subsystem is currently broken when used together with containers. We hence recommend turning it off entirely - when using systemd-nspawn by - booting with audit=0 on the kernel - command line, or by turning it off at kernel build - time. If auditing is enabled in the kernel operating - systems booted in an nspawn container might refuse - log-in attempts. + by booting with audit=0 on the + kernel command line, or by turning it off at kernel + build time. If auditing is enabled in the kernel + operating systems booted in an nspawn container might + refuse log-in attempts. -- cgit v1.2.3-54-g00ecf