X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=df318d7a43c02c6ac33bc181728b9aae00603dbe;hb=0452ffebbbb00a30894721666d81933425d182c7;hp=feafb31bc026f1da9f3ea3e3c3b80116365de039;hpb=e9dd9f9547350c7dc0473583b5c2228dc8f0ab76;p=elogind.git diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index feafb31bc..df318d7a4 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,42 @@ 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. + + + + + + + + Sets the mandatory + access control (MAC/SELinux) file + label to be used by virtual API file + systems in the container. + + + + + + + + Sets the mandatory + access control (MAC/SELinux) label to be used by + processes in the container. + + + @@ -250,16 +280,6 @@ - - - - - Makes the container appear in - other hierarchies than the name=systemd:/ one. - Takes a comma-separated list of controllers. - - - @@ -304,12 +324,22 @@ CAP_AUDIT_CONTROL. + + + + Specify one or more + additional capabilities to drop for + the container. This allows running the + container with fewer capabilities than + the default (see above). + + 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 +365,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 @@ -371,6 +401,33 @@ creates read-only bind mount. + + + + + Specifies an + environment variable assignment to + pass to the init process in the + container, in the format + NAME=VALUE. This + may be used to override the default + variables or to set additional + variables. This parameter may be used + more than once. + + + + + + + Turns off any status + output by the tool itself. When this + switch is used, then the only output + by nspawn will be the console output + of the container OS + itself. + + @@ -410,22 +467,35 @@ 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. + # mv ~/arch-tree /var/lib/container/arch +# systemctl enable systemd-nspawn@arch.service +# systemctl start systemd-nspawn@arch.service + + This makes the Arch Linux container part of the + multi-user.target on the host. + + + + + Example 5 + + # btrfs subvolume snapshot / /.tmp +# systemd-nspawn --private-network -D /.tmp -b + + This runs a copy of the host system in a + btrfs snapshot. + + + + Example 6 - # nsenter -m -u -i -n -p -t $PID + # chcon system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -R /srv/container +# systemd-nspawn -L system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -Z system_u:system_r:svirt_lxc_net_t:s0:c0,c1 -D /srv/container /bin/sh - nsenter1 - is part of - util-linux. - Kernel support for entering namespaces was added in - Linux 3.8. + This runs a container with SELinux sandbox labels. @@ -440,10 +510,11 @@ systemd1, chroot1, - unshare1, yum8, debootstrap8, - pacman8 + pacman8, + systemd.slice5, + machinectl1