X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=8adcd946b0438e6da634576eefc780a99ada068a;hp=554637d5f1919b0fc223860a3e47fe854c42fffb;hb=72536eb73674883f0c8522a241ecd86c032665db;hpb=4d62fb4298a5904a53f484636c91540d08f68765 diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 554637d5f..8adcd946b 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -49,7 +49,17 @@ - systemd-nspawn OPTIONS COMMAND ARGS + systemd-nspawn + OPTIONS + COMMAND + ARGS + + + + systemd-nspawn + -b + OPTIONS + ARGS @@ -114,7 +124,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 Options - If no arguments are passed the container is set - up and a shell started in it, otherwise the passed - command and arguments are executed in it. The - following options are understood: + If option is specified, the + arguments are used as arguments for the init + binary. Otherwise, COMMAND + specifies the program to launch in the container, and + the remaining arguments are used as arguments for this + program. If is not used and no + arguments are specifed, a shell is launched in the + container. + + The following options are understood: - + Prints a short help text and exits. @@ -147,8 +166,8 @@ - + Directory to use as file system root for the namespace @@ -158,18 +177,21 @@ - + Automatically search for an init binary and invoke it instead of a shell or a user supplied - program. + program. If this option is used, arguments + specified on the command line are used + as arguments for the init binary. + - + Run the command under specified user, create home @@ -192,8 +214,8 @@ - + Makes the container appear in other hierarchies than the name=systemd:/ one. @@ -262,13 +284,13 @@ not linked. If host, the journal files are stored on the host file system (beneath - /var/log/journal/<machine-id>) + /var/log/journal/machine-id) and the subdirectory is bind-mounted into the container at the same location. If guest, the journal files are stored on the guest file system (beneath - /var/log/journal/<machine-id>) + /var/log/journal/machine-id) and the subdirectory is symlinked into the host at the same location. If auto (the default), @@ -292,6 +314,26 @@ Equivalent to . + + + + + + Bind mount a file or + directory from the host into the + container. Either takes a path + argument -- in which case the + specified path will be mounted from + the host to the same path in the + container --, or a colon-separated + pair of paths -- in which case the + first specified path is the source in + the host, and the second path is the + destination in the container. The + option + creates read-only bind + mount. + @@ -318,7 +360,6 @@ distribution into the directory ~/debian-tree/ and then spawns a shell in a namespace container in it. - @@ -332,6 +373,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 +403,7 @@ systemd1, chroot1, + unshare1, yum8, debootstrap8, pacman8