X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=9d8db83e81ba9e845c0fe41f919e58c869b365de;hp=c95a7c0e9a5148600a1adf3e0a2340190b142a42;hb=89f7c8465cd1ab37347dd0c15920bce31e8225df;hpb=ba978d7b325998709fb19d368d290fa1dff37699 diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index c95a7c0e9..9d8db83e8 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -204,9 +204,12 @@ Automatically search for an init binary and invoke it instead of a shell or a user supplied - program. If this option is used, arguments - specified on the command line are used - as arguments for the init binary. + program. If this option is used, + arguments specified on the command + line are used as arguments for the + init binary. This option may not be + combined with + . @@ -249,23 +252,23 @@ - - + + - Sets the mandatory - access control (MAC/SELinux) file - label to be used by virtual API file - systems in the container. + Sets the SELinux + security context to be used to label + processes in the container. - - + + - Sets the mandatory - access control (MAC/SELinux) label to be used by - processes in the container. + Sets the SELinux security + context to be used to label files in + the virtual API file systems in the + container. @@ -424,8 +427,79 @@ 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. + of the container OS itself. + + + + + + Allows the container + to share certain system facilities + with the host. More specifically, this + turns off PID namespacing, UTS + namespacing and IPC namespacing, and + thus allows the guest to see and + interact more easily with processes + outside of the container. Note that + using this option makes it impossible + to start up a full Operating System in + the container, as an init system + cannot operate in this mode. It is + only useful to run specific programs + or applications this way, without + involving an init system in the + container. This option implies + . This + option may not be combined with + . + + + + + + Controls whether the + container is registered with + systemd-machined8. Takes + a boolean argument, defaults to + yes. This option + should be enabled when the container + runs a full Operating System (more + specifically: an init system), and is + useful to ensure that the container is + accessible via + machinectl1 + and shown by tools such as + ps1. If + the container does not run an init + system it is recommended to set this + option to no. Note + that + implies + . + + + + + + + Instead of creating a + transient scope unit to run the + container in, simply register the + service or scope unit + systemd-nspawn has + been invoked in in + systemd-machined8. This + has no effect if + is + used. This switch should be used if + systemd-nspawn is + invoked from within an a service unit, + and the service unit's sole purpose + is to run a single + systemd-nspawn + container. This option is not + available if run from a user + session. @@ -495,7 +569,7 @@ # 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 - This runs a container with SELinux sandbox labels. + This runs a container with SELinux sandbox security contexts.