X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=c2be6d5446babde16ca2ddb4dbc169d65cd5ff2e;hb=102d8f8169427cb68cdebf5ee0f0e07788e9c2b2;hp=feafb31bc026f1da9f3ea3e3c3b80116365de039;hpb=e9dd9f9547350c7dc0473583b5c2228dc8f0ab76;p=elogind.git diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index feafb31bc..c2be6d544 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 @@ -124,10 +123,10 @@ see each other. The PID namespace separation of the two containers is complete and the containers will share very few runtime objects except for the - underlying file system. It is however possible to - enter an existing container, see - Example 4 below. - + underlying file system. Use + machinectl1's + login command to request an + additional login prompt in a running container. systemd-nspawn implements the audit=0 on the kernel command line, or by turning it off at kernel - build time. If auditing is enabled in the kernel + build time. If auditing is enabled in the kernel, operating systems booted in an nspawn container might refuse log-in attempts. @@ -193,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. @@ -234,11 +233,21 @@ 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. + + + @@ -250,16 +259,6 @@ - - - - - Makes the container appear in - other hierarchies than the name=systemd:/ one. - Takes a comma-separated list of controllers. - - - @@ -309,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 @@ -335,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 @@ -410,24 +409,6 @@ boots an OS in a namespace container in it. - - Example 4 - - To enter the container, PID of one of the - processes sharing the new namespaces must be used. - systemd-nspawn prints the PID - (as viewed from the outside) of the launched process, - and it can be used to enter the container. - - # nsenter -m -u -i -n -p -t $PID - - nsenter1 - is part of - util-linux. - Kernel support for entering namespaces was added in - Linux 3.8. - - Exit status @@ -440,10 +421,11 @@ systemd1, chroot1, - unshare1, yum8, debootstrap8, - pacman8 + pacman8, + systemd.slice5, + machinectl1