From 1fd961211df69ce672252d543bf4777738647048 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Sat, 12 Jan 2013 16:55:04 -0500 Subject: nspawn: print PID and show how to enter the namespace systemd-nspawn will now print the PID of the child. An example showing how to enter the container is added to the man page. Support for nsenter without an explicit command was added in https://github.com/karelzak/util-linux/commit/5758069 (post v2.22.2). So this example requires both a new kernel and the latest util-linux. --- man/systemd-nspawn.xml | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) (limited to 'man/systemd-nspawn.xml') diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 6a01ffd450..5cba40bcd4 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -49,7 +49,10 @@ - systemd-nspawn OPTIONS COMMAND ARGS + systemd-nspawn + OPTIONS + COMMAND + ARGS @@ -114,7 +117,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. + underlying file system. It is however possible to + enter an existing container, see + Example 4 below. + systemd-nspawn implements the ~/debian-tree/ and then spawns a shell in a namespace container in it. - @@ -332,6 +337,24 @@ 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 -muinpt $PID + + nsenter1 + is part of + util-linux. + Kernel support for entering namespaces was added in + Linux 3.8. + + Exit status @@ -344,6 +367,7 @@ systemd1, chroot1, + unshare1, yum8, debootstrap8, pacman8 -- cgit v1.2.3-54-g00ecf