X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=75d2e6d72e2a0a9c91cf18cf782eef8039f196ba;hb=290c7324ca6ed22bcb6f4d644765aefeb47dc9de;hp=7d450f912c1c617c17d6bd41a32eb0d87374963a;hpb=79640424059328268b9fb6c5fa8eb777b27a177e;p=elogind.git diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 7d450f912..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 + + + + Specify one or more + additional capabilities to drop for + the container. This allows running the + container with fewer capabilities than + the default (see above). + + @@ -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