X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=7d450f912c1c617c17d6bd41a32eb0d87374963a;hp=cab5990a567b793f218201a3b109e71dcb0e04e4;hb=d1b38fac57d82f0249b9e581eb0d18175f6aa74a;hpb=f8964235e69f58225dec378437b1789744cd22a9 diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index cab5990a5..7d450f912 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -97,14 +97,13 @@ involved with boot and systems management. In contrast to - chroot1 - systemd-nspawn may be used to boot - full Linux-based operating systems in a - container. + chroot1 systemd-nspawn + may be used to boot full Linux-based operating systems + in a container. Use a tool like yum8, - debootstrap8 + debootstrap8, or pacman8 to set up an OS directory tree suitable as file system @@ -136,7 +135,7 @@ As a safety check systemd-nspawn will verify the - existance of /etc/os-release in + existence of /etc/os-release in the container tree before starting the container (see os-release5). It might be necessary to add this file to the container @@ -144,6 +143,19 @@ 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 + 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. + + Options @@ -180,7 +192,7 @@ Directory to use as file system root for the namespace - container. If omitted the current + container. If omitted, the current directory will be used. @@ -221,15 +233,25 @@ host, and is used to initialize the container's hostname (which the container can choose to override, - however). If not specified the last + however). If not specified, the last component of the root directory of the container is used. + + + + Make the container + part of the specified slice, instead + of the + machine.slice. + + + - Set the specified uuid + Set the specified UUID for the container. The init system will initialize /etc/machine-id @@ -237,16 +259,6 @@ - - - - - Makes the container appear in - other hierarchies than the name=systemd:/ one. - Takes a comma-separated list of controllers. - - - @@ -261,7 +273,7 @@ Mount the root file - system read only for the + system read-only for the container. @@ -270,7 +282,7 @@ List one or more additional capabilities to grant the - container. Takes a comma separated + container. Takes a comma-separated list of capability names, see capabilities7 for more information. Note that the @@ -296,7 +308,7 @@ Control whether the container's journal shall be made - visible to the host system. If enabled + visible to the host system. If enabled, allows viewing the container's journal files from the host (but not vice versa). Takes one of @@ -322,7 +334,7 @@ /var/log/journal exists, it will be bind mounted into the container. If the - subdirectory doesn't exist, no + subdirectory does not exist, no linking is performed. Effectively, booting a container once with guest or @@ -430,7 +442,8 @@ unshare1, yum8, debootstrap8, - pacman8 + pacman8, + systemd.slice5