X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=75d2e6d72e2a0a9c91cf18cf782eef8039f196ba;hb=71f2ab468d8413cffdb712083eb4d06dc8b2a271;hp=6264e48dbc9b69abf5310e3d6b0a59b355666b95;hpb=6b4991cfde6c0a0b62e836ca75ae362779c474d4;p=elogind.git diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 6264e48db..75d2e6d72 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -123,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. @@ -192,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. @@ -233,7 +233,7 @@ 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. @@ -303,12 +303,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 @@ -409,22 +419,16 @@ 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 - # 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. + This makes the Arch Linux container part of the + multi-user.target on the host. + @@ -439,11 +443,11 @@ systemd1, chroot1, - unshare1, yum8, debootstrap8, pacman8, - systemd.slice5 + systemd.slice5, + machinectl1