]>
Commit | Line | Data |
---|---|---|
f757855e | 1 | <?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*--> |
8f7a3c14 | 2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
12b42c76 | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> |
8f7a3c14 LP |
4 | |
5 | <!-- | |
6 | This file is part of systemd. | |
7 | ||
8 | Copyright 2010 Lennart Poettering | |
9 | ||
10 | systemd is free software; you can redistribute it and/or modify it | |
5430f7f2 LP |
11 | under the terms of the GNU Lesser General Public License as published by |
12 | the Free Software Foundation; either version 2.1 of the License, or | |
8f7a3c14 LP |
13 | (at your option) any later version. |
14 | ||
15 | systemd is distributed in the hope that it will be useful, but | |
16 | WITHOUT ANY WARRANTY; without even the implied warranty of | |
17 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | |
5430f7f2 | 18 | Lesser General Public License for more details. |
8f7a3c14 | 19 | |
5430f7f2 | 20 | You should have received a copy of the GNU Lesser General Public License |
8f7a3c14 LP |
21 | along with systemd; If not, see <http://www.gnu.org/licenses/>. |
22 | --> | |
23 | ||
dfdebb1b | 24 | <refentry id="systemd-nspawn" |
798d3a52 ZJS |
25 | xmlns:xi="http://www.w3.org/2001/XInclude"> |
26 | ||
27 | <refentryinfo> | |
28 | <title>systemd-nspawn</title> | |
29 | <productname>systemd</productname> | |
30 | ||
31 | <authorgroup> | |
32 | <author> | |
33 | <contrib>Developer</contrib> | |
34 | <firstname>Lennart</firstname> | |
35 | <surname>Poettering</surname> | |
36 | <email>lennart@poettering.net</email> | |
37 | </author> | |
38 | </authorgroup> | |
39 | </refentryinfo> | |
40 | ||
41 | <refmeta> | |
42 | <refentrytitle>systemd-nspawn</refentrytitle> | |
43 | <manvolnum>1</manvolnum> | |
44 | </refmeta> | |
45 | ||
46 | <refnamediv> | |
47 | <refname>systemd-nspawn</refname> | |
48 | <refpurpose>Spawn a namespace container for debugging, testing and building</refpurpose> | |
49 | </refnamediv> | |
50 | ||
51 | <refsynopsisdiv> | |
52 | <cmdsynopsis> | |
53 | <command>systemd-nspawn</command> | |
54 | <arg choice="opt" rep="repeat">OPTIONS</arg> | |
55 | <arg choice="opt"><replaceable>COMMAND</replaceable> | |
56 | <arg choice="opt" rep="repeat">ARGS</arg> | |
57 | </arg> | |
58 | </cmdsynopsis> | |
59 | <cmdsynopsis> | |
60 | <command>systemd-nspawn</command> | |
4447e799 | 61 | <arg choice="plain">--boot</arg> |
798d3a52 ZJS |
62 | <arg choice="opt" rep="repeat">OPTIONS</arg> |
63 | <arg choice="opt" rep="repeat">ARGS</arg> | |
64 | </cmdsynopsis> | |
65 | </refsynopsisdiv> | |
66 | ||
67 | <refsect1> | |
68 | <title>Description</title> | |
69 | ||
b09c0bba LP |
70 | <para><command>systemd-nspawn</command> may be used to run a command or OS in a light-weight namespace |
71 | container. In many ways it is similar to <citerefentry | |
72 | project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, but more powerful | |
73 | since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and | |
74 | the host and domain name.</para> | |
75 | ||
5164c3b4 | 76 | <para><command>systemd-nspawn</command> may be invoked on any directory tree containing an operating system tree, |
b09c0bba | 77 | using the <option>--directory=</option> command line option. By using the <option>--machine=</option> option an OS |
5164c3b4 | 78 | tree is automatically searched for in a couple of locations, most importantly in |
b09c0bba LP |
79 | <filename>/var/lib/machines</filename>, the suggested directory to place container images installed on the |
80 | system.</para> | |
81 | ||
82 | <para>In contrast to <citerefentry | |
83 | project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>systemd-nspawn</command> | |
84 | may be used to boot full Linux-based operating systems in a container.</para> | |
85 | ||
86 | <para><command>systemd-nspawn</command> limits access to various kernel interfaces in the container to read-only, | |
87 | such as <filename>/sys</filename>, <filename>/proc/sys</filename> or <filename>/sys/fs/selinux</filename>. The | |
88 | host's network interfaces and the system clock may not be changed from within the container. Device nodes may not | |
89 | be created. The host system cannot be rebooted and kernel modules may not be loaded from within the | |
798d3a52 ZJS |
90 | container.</para> |
91 | ||
b09c0bba LP |
92 | <para>Use a tool like <citerefentry |
93 | project='mankier'><refentrytitle>dnf</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry | |
94 | project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>, or | |
95 | <citerefentry project='archlinux'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry> to | |
96 | set up an OS directory tree suitable as file system hierarchy for <command>systemd-nspawn</command> containers. See | |
97 | the Examples section below for details on suitable invocation of these commands.</para> | |
98 | ||
99 | <para>As a safety check <command>systemd-nspawn</command> will verify the existence of | |
100 | <filename>/usr/lib/os-release</filename> or <filename>/etc/os-release</filename> in the container tree before | |
101 | starting the container (see | |
102 | <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry>). It might be | |
103 | necessary to add this file to the container tree manually if the OS of the container is too old to contain this | |
798d3a52 | 104 | file out-of-the-box.</para> |
b09c0bba LP |
105 | |
106 | <para><command>systemd-nspawn</command> may be invoked directly from the interactive command line or run as system | |
107 | service in the background. In this mode each container instance runs as its own service instance; a default | |
108 | template unit file <filename>systemd-nspawn@.service</filename> is provided to make this easy, taking the container | |
109 | name as instance identifier. Note that different default options apply when <command>systemd-nspawn</command> is | |
6dd6a9c4 | 110 | invoked by the template unit file than interactively on the command line. Most importantly the template unit file |
b09c0bba | 111 | makes use of the <option>--boot</option> which is not the default in case <command>systemd-nspawn</command> is |
6dd6a9c4 | 112 | invoked from the interactive command line. Further differences with the defaults are documented along with the |
b09c0bba LP |
113 | various supported options below.</para> |
114 | ||
115 | <para>The <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> tool may | |
116 | be used to execute a number of operations on containers. In particular it provides easy-to-use commands to run | |
117 | containers as system services using the <filename>systemd-nspawn@.service</filename> template unit | |
118 | file.</para> | |
119 | ||
120 | <para>Along with each container a settings file with the <filename>.nspawn</filename> suffix may exist, containing | |
121 | additional settings to apply when running the container. See | |
122 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry> for | |
123 | details. Settings files override the default options used by the <filename>systemd-nspawn@.service</filename> | |
124 | template unit file, making it usually unnecessary to alter this template file directly.</para> | |
125 | ||
126 | <para>Note that <command>systemd-nspawn</command> will mount file systems private to the container to | |
127 | <filename>/dev</filename>, <filename>/run</filename> and similar. These will not be visible outside of the | |
128 | container, and their contents will be lost when the container exits.</para> | |
129 | ||
130 | <para>Note that running two <command>systemd-nspawn</command> containers from the same directory tree will not make | |
131 | processes in them see each other. The PID namespace separation of the two containers is complete and the containers | |
132 | will share very few runtime objects except for the underlying file system. Use | |
133 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s | |
134 | <command>login</command> or <command>shell</command> commands to request an additional login session in a running | |
135 | container.</para> | |
136 | ||
137 | <para><command>systemd-nspawn</command> implements the <ulink | |
138 | url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container Interface</ulink> | |
139 | specification.</para> | |
140 | ||
141 | <para>While running, containers invoked with <command>systemd-nspawn</command> are registered with the | |
142 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry> service that | |
143 | keeps track of running containers, and provides programming interfaces to interact with them.</para> | |
798d3a52 ZJS |
144 | </refsect1> |
145 | ||
146 | <refsect1> | |
147 | <title>Options</title> | |
148 | ||
149 | <para>If option <option>-b</option> is specified, the arguments | |
150 | are used as arguments for the init binary. Otherwise, | |
151 | <replaceable>COMMAND</replaceable> specifies the program to launch | |
152 | in the container, and the remaining arguments are used as | |
b09c0bba | 153 | arguments for this program. If <option>--boot</option> is not used and |
ff9b60f3 | 154 | no arguments are specified, a shell is launched in the |
798d3a52 ZJS |
155 | container.</para> |
156 | ||
157 | <para>The following options are understood:</para> | |
158 | ||
159 | <variablelist> | |
160 | <varlistentry> | |
161 | <term><option>-D</option></term> | |
162 | <term><option>--directory=</option></term> | |
163 | ||
164 | <listitem><para>Directory to use as file system root for the | |
165 | container.</para> | |
166 | ||
167 | <para>If neither <option>--directory=</option>, nor | |
168 | <option>--image=</option> is specified the directory is | |
32b64cce RM |
169 | determined by searching for a directory named the same as the |
170 | machine name specified with <option>--machine=</option>. See | |
171 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
172 | section "Files and Directories" for the precise search path.</para> | |
173 | ||
174 | <para>If neither <option>--directory=</option>, | |
175 | <option>--image=</option>, nor <option>--machine=</option> | |
176 | are specified, the current directory will | |
177 | be used. May not be specified together with | |
798d3a52 ZJS |
178 | <option>--image=</option>.</para></listitem> |
179 | </varlistentry> | |
180 | ||
181 | <varlistentry> | |
182 | <term><option>--template=</option></term> | |
183 | ||
17cbb288 LP |
184 | <listitem><para>Directory or <literal>btrfs</literal> subvolume to use as template for the container's root |
185 | directory. If this is specified and the container's root directory (as configured by | |
186 | <option>--directory=</option>) does not yet exist it is created as <literal>btrfs</literal> snapshot (if | |
187 | supported) or plain directory (otherwise) and populated from this template tree. Ideally, the specified | |
188 | template path refers to the root of a <literal>btrfs</literal> subvolume, in which case a simple copy-on-write | |
189 | snapshot is taken, and populating the root directory is instant. If the specified template path does not refer | |
190 | to the root of a <literal>btrfs</literal> subvolume (or not even to a <literal>btrfs</literal> file system at | |
191 | all), the tree is copied (though possibly in a copy-on-write scheme — if the file system supports that), which | |
192 | can be substantially more time-consuming. May not be specified together with <option>--image=</option> or | |
3fe22bb4 LP |
193 | <option>--ephemeral</option>.</para> |
194 | ||
195 | <para>Note that this switch leaves host name, machine ID and | |
196 | all other settings that could identify the instance | |
197 | unmodified.</para></listitem> | |
798d3a52 ZJS |
198 | </varlistentry> |
199 | ||
200 | <varlistentry> | |
201 | <term><option>-x</option></term> | |
202 | <term><option>--ephemeral</option></term> | |
203 | ||
0f3be6ca LP |
204 | <listitem><para>If specified, the container is run with a temporary snapshot of its file system that is removed |
205 | immediately when the container terminates. May not be specified together with | |
3fe22bb4 LP |
206 | <option>--template=</option>.</para> |
207 | <para>Note that this switch leaves host name, machine ID and | |
208 | all other settings that could identify the instance | |
209 | unmodified.</para></listitem> | |
798d3a52 ZJS |
210 | </varlistentry> |
211 | ||
212 | <varlistentry> | |
213 | <term><option>-i</option></term> | |
214 | <term><option>--image=</option></term> | |
215 | ||
216 | <listitem><para>Disk image to mount the root directory for the | |
217 | container from. Takes a path to a regular file or to a block | |
218 | device node. The file or block device must contain | |
219 | either:</para> | |
220 | ||
221 | <itemizedlist> | |
222 | <listitem><para>An MBR partition table with a single | |
223 | partition of type 0x83 that is marked | |
224 | bootable.</para></listitem> | |
225 | ||
226 | <listitem><para>A GUID partition table (GPT) with a single | |
227 | partition of type | |
228 | 0fc63daf-8483-4772-8e79-3d69d8477de4.</para></listitem> | |
229 | ||
230 | <listitem><para>A GUID partition table (GPT) with a marked | |
231 | root partition which is mounted as the root directory of the | |
232 | container. Optionally, GPT images may contain a home and/or | |
233 | a server data partition which are mounted to the appropriate | |
234 | places in the container. All these partitions must be | |
235 | identified by the partition types defined by the <ulink | |
236 | url="http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/">Discoverable | |
237 | Partitions Specification</ulink>.</para></listitem> | |
58abb66f LP |
238 | |
239 | <listitem><para>No partition table, and a single file system spanning the whole image.</para></listitem> | |
798d3a52 ZJS |
240 | </itemizedlist> |
241 | ||
0f3be6ca LP |
242 | <para>On GPT images, if an EFI System Partition (ESP) is discovered, it is automatically mounted to |
243 | <filename>/efi</filename> (or <filename>/boot</filename> as fallback) in case a directory by this name exists | |
244 | and is empty.</para> | |
245 | ||
58abb66f LP |
246 | <para>Partitions encrypted with LUKS are automatically decrypted. Also, on GPT images dm-verity data integrity |
247 | hash partitions are set up if the root hash for them is specified using the <option>--root-hash=</option> | |
248 | option.</para> | |
249 | ||
0f3be6ca LP |
250 | <para>Any other partitions, such as foreign partitions or swap partitions are not mounted. May not be specified |
251 | together with <option>--directory=</option>, <option>--template=</option>.</para></listitem> | |
798d3a52 | 252 | </varlistentry> |
58abb66f LP |
253 | |
254 | <varlistentry> | |
255 | <term><option>--root-hash=</option></term> | |
256 | ||
257 | <listitem><para>Takes a data integrity (dm-verity) root hash specified in hexadecimal. This option enables data | |
258 | integrity checks using dm-verity, if the used image contains the appropriate integrity data (see above). The | |
259 | specified hash must match the root hash of integrity data, and is usually at least 256bits (and hence 64 | |
260 | hexadecimal characters) long (in case of SHA256 for example). If this option is not specified, but a file with | |
261 | the <filename>.roothash</filename> suffix is found next to the image file, bearing otherwise the same name the | |
262 | root hash is read from it and automatically used.</para></listitem> | |
263 | </varlistentry> | |
798d3a52 | 264 | |
7732f92b LP |
265 | <varlistentry> |
266 | <term><option>-a</option></term> | |
267 | <term><option>--as-pid2</option></term> | |
268 | ||
269 | <listitem><para>Invoke the shell or specified program as process ID (PID) 2 instead of PID 1 (init). By | |
270 | default, if neither this option nor <option>--boot</option> is used, the selected binary is run as process with | |
271 | PID 1, a mode only suitable for programs that are aware of the special semantics that the process with PID 1 | |
272 | has on UNIX. For example, it needs to reap all processes reparented to it, and should implement | |
273 | <command>sysvinit</command> compatible signal handling (specifically: it needs to reboot on SIGINT, reexecute | |
274 | on SIGTERM, reload configuration on SIGHUP, and so on). With <option>--as-pid2</option> a minimal stub init | |
275 | process is run as PID 1 and the selected binary is executed as PID 2 (and hence does not need to implement any | |
276 | special semantics). The stub init process will reap processes as necessary and react appropriately to | |
277 | signals. It is recommended to use this mode to invoke arbitrary commands in containers, unless they have been | |
278 | modified to run correctly as PID 1. Or in other words: this switch should be used for pretty much all commands, | |
279 | except when the command refers to an init or shell implementation, as these are generally capable of running | |
a6b5216c | 280 | correctly as PID 1. This option may not be combined with <option>--boot</option>.</para> |
7732f92b LP |
281 | </listitem> |
282 | </varlistentry> | |
283 | ||
798d3a52 ZJS |
284 | <varlistentry> |
285 | <term><option>-b</option></term> | |
286 | <term><option>--boot</option></term> | |
287 | ||
7732f92b LP |
288 | <listitem><para>Automatically search for an init binary and invoke it as PID 1, instead of a shell or a user |
289 | supplied program. If this option is used, arguments specified on the command line are used as arguments for the | |
a6b5216c | 290 | init binary. This option may not be combined with <option>--as-pid2</option>.</para> |
7732f92b LP |
291 | |
292 | <para>The following table explains the different modes of invocation and relationship to | |
293 | <option>--as-pid2</option> (see above):</para> | |
294 | ||
295 | <table> | |
296 | <title>Invocation Mode</title> | |
297 | <tgroup cols='2' align='left' colsep='1' rowsep='1'> | |
298 | <colspec colname="switch" /> | |
299 | <colspec colname="explanation" /> | |
300 | <thead> | |
301 | <row> | |
302 | <entry>Switch</entry> | |
303 | <entry>Explanation</entry> | |
304 | </row> | |
305 | </thead> | |
306 | <tbody> | |
307 | <row> | |
308 | <entry>Neither <option>--as-pid2</option> nor <option>--boot</option> specified</entry> | |
4447e799 | 309 | <entry>The passed parameters are interpreted as the command line, which is executed as PID 1 in the container.</entry> |
7732f92b LP |
310 | </row> |
311 | ||
312 | <row> | |
313 | <entry><option>--as-pid2</option> specified</entry> | |
4447e799 | 314 | <entry>The passed parameters are interpreted as the command line, which is executed as PID 2 in the container. A stub init process is run as PID 1.</entry> |
7732f92b LP |
315 | </row> |
316 | ||
317 | <row> | |
318 | <entry><option>--boot</option> specified</entry> | |
319 | <entry>An init binary as automatically searched and run as PID 1 in the container. The passed parameters are used as invocation parameters for this process.</entry> | |
320 | </row> | |
321 | ||
322 | </tbody> | |
323 | </tgroup> | |
324 | </table> | |
b09c0bba LP |
325 | |
326 | <para>Note that <option>--boot</option> is the default mode of operation if the | |
327 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
7732f92b | 328 | </listitem> |
798d3a52 ZJS |
329 | </varlistentry> |
330 | ||
5f932eb9 LP |
331 | <varlistentry> |
332 | <term><option>--chdir=</option></term> | |
333 | ||
334 | <listitem><para>Change to the specified working directory before invoking the process in the container. Expects | |
335 | an absolute path in the container's file system namespace.</para></listitem> | |
336 | </varlistentry> | |
337 | ||
798d3a52 ZJS |
338 | <varlistentry> |
339 | <term><option>-u</option></term> | |
340 | <term><option>--user=</option></term> | |
341 | ||
342 | <listitem><para>After transitioning into the container, change | |
343 | to the specified user-defined in the container's user | |
344 | database. Like all other systemd-nspawn features, this is not | |
345 | a security feature and provides protection against accidental | |
346 | destructive operations only.</para></listitem> | |
347 | </varlistentry> | |
348 | ||
349 | <varlistentry> | |
350 | <term><option>-M</option></term> | |
351 | <term><option>--machine=</option></term> | |
352 | ||
353 | <listitem><para>Sets the machine name for this container. This | |
354 | name may be used to identify this container during its runtime | |
355 | (for example in tools like | |
356 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
357 | and similar), and is used to initialize the container's | |
358 | hostname (which the container can choose to override, | |
359 | however). If not specified, the last component of the root | |
360 | directory path of the container is used, possibly suffixed | |
361 | with a random identifier in case <option>--ephemeral</option> | |
362 | mode is selected. If the root directory selected is the host's | |
363 | root directory the host's hostname is used as default | |
364 | instead.</para></listitem> | |
365 | </varlistentry> | |
366 | ||
367 | <varlistentry> | |
368 | <term><option>--uuid=</option></term> | |
369 | ||
370 | <listitem><para>Set the specified UUID for the container. The | |
371 | init system will initialize | |
372 | <filename>/etc/machine-id</filename> from this if this file is | |
e01ff70a MS |
373 | not set yet. Note that this option takes effect only if |
374 | <filename>/etc/machine-id</filename> in the container is | |
375 | unpopulated.</para></listitem> | |
798d3a52 ZJS |
376 | </varlistentry> |
377 | ||
378 | <varlistentry> | |
379 | <term><option>--slice=</option></term> | |
380 | ||
381 | <listitem><para>Make the container part of the specified | |
382 | slice, instead of the default | |
f36933fe LP |
383 | <filename>machine.slice</filename>. This is only applies if |
384 | the machine is run in its own scope unit, i.e. if | |
385 | <option>--keep-unit</option> is not used.</para> | |
386 | </listitem> | |
387 | </varlistentry> | |
388 | ||
389 | <varlistentry> | |
390 | <term><option>--property=</option></term> | |
391 | ||
392 | <listitem><para>Set a unit property on the scope unit to | |
393 | register for the machine. This only applies if the machine is | |
394 | run in its own scope unit, i.e. if | |
395 | <option>--keep-unit</option> is not used. Takes unit property | |
396 | assignments in the same format as <command>systemctl | |
397 | set-property</command>. This is useful to set memory limits | |
398 | and similar for machines.</para> | |
798d3a52 ZJS |
399 | </listitem> |
400 | </varlistentry> | |
401 | ||
03cfe0d5 LP |
402 | <varlistentry> |
403 | <term><option>--private-users=</option></term> | |
404 | ||
d2e5535f LP |
405 | <listitem><para>Controls user namespacing. If enabled, the container will run with its own private set of UNIX |
406 | user and group ids (UIDs and GIDs). This involves mapping the private UIDs/GIDs used in the container (starting | |
407 | with the container's root user 0 and up) to a range of UIDs/GIDs on the host that are not used for other | |
408 | purposes (usually in the range beyond the host's UID/GID 65536). The parameter may be specified as follows:</para> | |
409 | ||
410 | <orderedlist> | |
2dd67817 | 411 | <listitem><para>If one or two colon-separated numbers are specified, user namespacing is turned on. The first |
ae209204 ZJS |
412 | parameter specifies the first host UID/GID to assign to the container, the second parameter specifies the |
413 | number of host UIDs/GIDs to assign to the container. If the second parameter is omitted, 65536 UIDs/GIDs are | |
414 | assigned.</para></listitem> | |
415 | ||
416 | <listitem><para>If the parameter is omitted, or true, user namespacing is turned on. The UID/GID range to | |
417 | use is determined automatically from the file ownership of the root directory of the container's directory | |
418 | tree. To use this option, make sure to prepare the directory tree in advance, and ensure that all files and | |
419 | directories in it are owned by UIDs/GIDs in the range you'd like to use. Also, make sure that used file ACLs | |
420 | exclusively reference UIDs/GIDs in the appropriate range. If this mode is used the number of UIDs/GIDs | |
421 | assigned to the container for use is 65536, and the UID/GID of the root directory must be a multiple of | |
422 | 65536.</para></listitem> | |
423 | ||
424 | <listitem><para>If the parameter is false, user namespacing is turned off. This is the default.</para> | |
425 | </listitem> | |
426 | ||
427 | <listitem><para>The special value <literal>pick</literal> turns on user namespacing. In this case the UID/GID | |
428 | range is automatically chosen. As first step, the file owner of the root directory of the container's | |
429 | directory tree is read, and it is checked that it is currently not used by the system otherwise (in | |
430 | particular, that no other container is using it). If this check is successful, the UID/GID range determined | |
2dd67817 | 431 | this way is used, similar to the behavior if "yes" is specified. If the check is not successful (and thus |
ae209204 ZJS |
432 | the UID/GID range indicated in the root directory's file owner is already used elsewhere) a new – currently |
433 | unused – UID/GID range of 65536 UIDs/GIDs is randomly chosen between the host UID/GIDs of 524288 and | |
434 | 1878982656, always starting at a multiple of 65536. This setting implies | |
435 | <option>--private-users-chown</option> (see below), which has the effect that the files and directories in | |
436 | the container's directory tree will be owned by the appropriate users of the range picked. Using this option | |
2dd67817 | 437 | makes user namespace behavior fully automatic. Note that the first invocation of a previously unused |
ae209204 ZJS |
438 | container image might result in picking a new UID/GID range for it, and thus in the (possibly expensive) file |
439 | ownership adjustment operation. However, subsequent invocations of the container will be cheap (unless of | |
440 | course the picked UID/GID range is assigned to a different use by then).</para></listitem> | |
d2e5535f LP |
441 | </orderedlist> |
442 | ||
443 | <para>It is recommended to assign at least 65536 UIDs/GIDs to each container, so that the usable UID/GID range in the | |
444 | container covers 16 bit. For best security, do not assign overlapping UID/GID ranges to multiple containers. It is | |
445 | hence a good idea to use the upper 16 bit of the host 32-bit UIDs/GIDs as container identifier, while the lower 16 | |
2dd67817 | 446 | bit encode the container UID/GID used. This is in fact the behavior enforced by the |
d2e5535f LP |
447 | <option>--private-users=pick</option> option.</para> |
448 | ||
449 | <para>When user namespaces are used, the GID range assigned to each container is always chosen identical to the | |
450 | UID range.</para> | |
451 | ||
452 | <para>In most cases, using <option>--private-users=pick</option> is the recommended option as it enhances | |
453 | container security massively and operates fully automatically in most cases.</para> | |
454 | ||
455 | <para>Note that the picked UID/GID range is not written to <filename>/etc/passwd</filename> or | |
456 | <filename>/etc/group</filename>. In fact, the allocation of the range is not stored persistently anywhere, | |
457 | except in the file ownership of the files and directories of the container.</para></listitem> | |
03cfe0d5 LP |
458 | </varlistentry> |
459 | ||
d2e5535f LP |
460 | <varlistentry> |
461 | <term><option>--private-users-chown</option></term> | |
462 | ||
463 | <listitem><para>If specified, all files and directories in the container's directory tree will adjusted so that | |
464 | they are owned to the appropriate UIDs/GIDs selected for the container (see above). This operation is | |
465 | potentially expensive, as it involves descending and iterating through the full directory tree of the | |
466 | container. Besides actual file ownership, file ACLs are adjusted as well.</para> | |
467 | ||
468 | <para>This option is implied if <option>--private-users=pick</option> is used. This option has no effect if | |
469 | user namespacing is not used.</para></listitem> | |
470 | </varlistentry> | |
03cfe0d5 | 471 | |
6265bde2 ZJS |
472 | <varlistentry> |
473 | <term><option>-U</option></term> | |
474 | ||
475 | <listitem><para>If the kernel supports the user namespaces feature, equivalent to | |
476 | <option>--private-users=pick --private-users-chown</option>, otherwise equivalent to | |
477 | <option>--private-users=no</option>.</para> | |
478 | ||
479 | <para>Note that <option>-U</option> is the default if the | |
480 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
481 | ||
482 | <para>Note: it is possible to undo the effect of <option>--private-users-chown</option> (or | |
483 | <option>-U</option>) on the file system by redoing the operation with the first UID of 0:</para> | |
484 | ||
485 | <programlisting>systemd-nspawn … --private-users=0 --private-users-chown</programlisting> | |
486 | </listitem> | |
487 | </varlistentry> | |
488 | ||
798d3a52 ZJS |
489 | <varlistentry> |
490 | <term><option>--private-network</option></term> | |
491 | ||
492 | <listitem><para>Disconnect networking of the container from | |
493 | the host. This makes all network interfaces unavailable in the | |
494 | container, with the exception of the loopback device and those | |
495 | specified with <option>--network-interface=</option> and | |
496 | configured with <option>--network-veth</option>. If this | |
497 | option is specified, the CAP_NET_ADMIN capability will be | |
498 | added to the set of capabilities the container retains. The | |
499 | latter may be disabled by using | |
500 | <option>--drop-capability=</option>.</para></listitem> | |
501 | </varlistentry> | |
502 | ||
503 | <varlistentry> | |
504 | <term><option>--network-interface=</option></term> | |
505 | ||
506 | <listitem><para>Assign the specified network interface to the | |
507 | container. This will remove the specified interface from the | |
508 | calling namespace and place it in the container. When the | |
509 | container terminates, it is moved back to the host namespace. | |
510 | Note that <option>--network-interface=</option> implies | |
511 | <option>--private-network</option>. This option may be used | |
512 | more than once to add multiple network interfaces to the | |
513 | container.</para></listitem> | |
514 | </varlistentry> | |
515 | ||
516 | <varlistentry> | |
517 | <term><option>--network-macvlan=</option></term> | |
518 | ||
519 | <listitem><para>Create a <literal>macvlan</literal> interface | |
520 | of the specified Ethernet network interface and add it to the | |
521 | container. A <literal>macvlan</literal> interface is a virtual | |
522 | interface that adds a second MAC address to an existing | |
523 | physical Ethernet link. The interface in the container will be | |
524 | named after the interface on the host, prefixed with | |
525 | <literal>mv-</literal>. Note that | |
526 | <option>--network-macvlan=</option> implies | |
527 | <option>--private-network</option>. This option may be used | |
528 | more than once to add multiple network interfaces to the | |
529 | container.</para></listitem> | |
530 | </varlistentry> | |
531 | ||
532 | <varlistentry> | |
533 | <term><option>--network-ipvlan=</option></term> | |
534 | ||
535 | <listitem><para>Create an <literal>ipvlan</literal> interface | |
536 | of the specified Ethernet network interface and add it to the | |
537 | container. An <literal>ipvlan</literal> interface is a virtual | |
538 | interface, similar to a <literal>macvlan</literal> interface, | |
539 | which uses the same MAC address as the underlying interface. | |
540 | The interface in the container will be named after the | |
541 | interface on the host, prefixed with <literal>iv-</literal>. | |
542 | Note that <option>--network-ipvlan=</option> implies | |
543 | <option>--private-network</option>. This option may be used | |
544 | more than once to add multiple network interfaces to the | |
545 | container.</para></listitem> | |
546 | </varlistentry> | |
547 | ||
548 | <varlistentry> | |
549 | <term><option>-n</option></term> | |
550 | <term><option>--network-veth</option></term> | |
551 | ||
5e7423ff LP |
552 | <listitem><para>Create a virtual Ethernet link (<literal>veth</literal>) between host and container. The host |
553 | side of the Ethernet link will be available as a network interface named after the container's name (as | |
554 | specified with <option>--machine=</option>), prefixed with <literal>ve-</literal>. The container side of the | |
555 | Ethernet link will be named <literal>host0</literal>. The <option>--network-veth</option> option implies | |
556 | <option>--private-network</option>.</para> | |
557 | ||
558 | <para>Note that | |
559 | <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> | |
560 | includes by default a network file <filename>/usr/lib/systemd/network/80-container-ve.network</filename> | |
561 | matching the host-side interfaces created this way, which contains settings to enable automatic address | |
562 | provisioning on the created virtual link via DHCP, as well as automatic IP routing onto the host's external | |
563 | network interfaces. It also contains <filename>/usr/lib/systemd/network/80-container-host0.network</filename> | |
564 | matching the container-side interface created this way, containing settings to enable client side address | |
565 | assignment via DHCP. In case <filename>systemd-networkd</filename> is running on both the host and inside the | |
566 | container, automatic IP communication from the container to the host is thus available, with further | |
567 | connectivity to the external network.</para> | |
b09c0bba LP |
568 | |
569 | <para>Note that <option>--network-veth</option> is the default if the | |
570 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
5e7423ff | 571 | </listitem> |
798d3a52 ZJS |
572 | </varlistentry> |
573 | ||
f6d6bad1 LP |
574 | <varlistentry> |
575 | <term><option>--network-veth-extra=</option></term> | |
576 | ||
577 | <listitem><para>Adds an additional virtual Ethernet link | |
578 | between host and container. Takes a colon-separated pair of | |
579 | host interface name and container interface name. The latter | |
580 | may be omitted in which case the container and host sides will | |
581 | be assigned the same name. This switch is independent of | |
ccddd104 | 582 | <option>--network-veth</option>, and — in contrast — may be |
f6d6bad1 LP |
583 | used multiple times, and allows configuration of the network |
584 | interface names. Note that <option>--network-bridge=</option> | |
585 | has no effect on interfaces created with | |
586 | <option>--network-veth-extra=</option>.</para></listitem> | |
587 | </varlistentry> | |
588 | ||
798d3a52 ZJS |
589 | <varlistentry> |
590 | <term><option>--network-bridge=</option></term> | |
591 | ||
5e7423ff LP |
592 | <listitem><para>Adds the host side of the Ethernet link created with <option>--network-veth</option> to the |
593 | specified Ethernet bridge interface. Expects a valid network interface name of a bridge device as | |
594 | argument. Note that <option>--network-bridge=</option> implies <option>--network-veth</option>. If this option | |
595 | is used, the host side of the Ethernet link will use the <literal>vb-</literal> prefix instead of | |
798d3a52 ZJS |
596 | <literal>ve-</literal>.</para></listitem> |
597 | </varlistentry> | |
598 | ||
938d2579 LP |
599 | <varlistentry> |
600 | <term><option>--network-zone=</option></term> | |
601 | ||
602 | <listitem><para>Creates a virtual Ethernet link (<literal>veth</literal>) to the container and adds it to an | |
603 | automatically managed Ethernet bridge interface. The bridge interface is named after the passed argument, | |
604 | prefixed with <literal>vz-</literal>. The bridge interface is automatically created when the first container | |
605 | configured for its name is started, and is automatically removed when the last container configured for its | |
606 | name exits. Hence, each bridge interface configured this way exists only as long as there's at least one | |
607 | container referencing it running. This option is very similar to <option>--network-bridge=</option>, besides | |
608 | this automatic creation/removal of the bridge device.</para> | |
609 | ||
610 | <para>This setting makes it easy to place multiple related containers on a common, virtual Ethernet-based | |
611 | broadcast domain, here called a "zone". Each container may only be part of one zone, but each zone may contain | |
612 | any number of containers. Each zone is referenced by its name. Names may be chosen freely (as long as they form | |
613 | valid network interface names when prefixed with <literal>vz-</literal>), and it is sufficient to pass the same | |
614 | name to the <option>--network-zones=</option> switch of the various concurrently running containers to join | |
615 | them in one zone.</para> | |
616 | ||
617 | <para>Note that | |
618 | <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> | |
619 | includes by default a network file <filename>/usr/lib/systemd/network/80-container-vz.network</filename> | |
620 | matching the bridge interfaces created this way, which contains settings to enable automatic address | |
621 | provisioning on the created virtual network via DHCP, as well as automatic IP routing onto the host's external | |
622 | network interfaces. Using <option>--network-zone=</option> is hence in most cases fully automatic and | |
623 | sufficient to connect multiple local containers in a joined broadcast domain to the host, with further | |
624 | connectivity to the external network.</para> | |
625 | </listitem> | |
626 | </varlistentry> | |
627 | ||
798d3a52 ZJS |
628 | <varlistentry> |
629 | <term><option>-p</option></term> | |
630 | <term><option>--port=</option></term> | |
631 | ||
632 | <listitem><para>If private networking is enabled, maps an IP | |
633 | port on the host onto an IP port on the container. Takes a | |
634 | protocol specifier (either <literal>tcp</literal> or | |
635 | <literal>udp</literal>), separated by a colon from a host port | |
636 | number in the range 1 to 65535, separated by a colon from a | |
637 | container port number in the range from 1 to 65535. The | |
638 | protocol specifier and its separating colon may be omitted, in | |
639 | which case <literal>tcp</literal> is assumed. The container | |
7c918141 | 640 | port number and its colon may be omitted, in which case the |
798d3a52 | 641 | same port as the host port is implied. This option is only |
a8eaaee7 | 642 | supported if private networking is used, such as with |
938d2579 | 643 | <option>--network-veth</option>, <option>--network-zone=</option> |
798d3a52 ZJS |
644 | <option>--network-bridge=</option>.</para></listitem> |
645 | </varlistentry> | |
646 | ||
647 | <varlistentry> | |
648 | <term><option>-Z</option></term> | |
649 | <term><option>--selinux-context=</option></term> | |
650 | ||
651 | <listitem><para>Sets the SELinux security context to be used | |
652 | to label processes in the container.</para> | |
653 | </listitem> | |
654 | </varlistentry> | |
655 | ||
656 | <varlistentry> | |
657 | <term><option>-L</option></term> | |
658 | <term><option>--selinux-apifs-context=</option></term> | |
659 | ||
660 | <listitem><para>Sets the SELinux security context to be used | |
661 | to label files in the virtual API file systems in the | |
662 | container.</para> | |
663 | </listitem> | |
664 | </varlistentry> | |
665 | ||
666 | <varlistentry> | |
667 | <term><option>--capability=</option></term> | |
668 | ||
669 | <listitem><para>List one or more additional capabilities to | |
670 | grant the container. Takes a comma-separated list of | |
671 | capability names, see | |
672 | <citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry> | |
673 | for more information. Note that the following capabilities | |
674 | will be granted in any way: CAP_CHOWN, CAP_DAC_OVERRIDE, | |
675 | CAP_DAC_READ_SEARCH, CAP_FOWNER, CAP_FSETID, CAP_IPC_OWNER, | |
676 | CAP_KILL, CAP_LEASE, CAP_LINUX_IMMUTABLE, | |
677 | CAP_NET_BIND_SERVICE, CAP_NET_BROADCAST, CAP_NET_RAW, | |
678 | CAP_SETGID, CAP_SETFCAP, CAP_SETPCAP, CAP_SETUID, | |
679 | CAP_SYS_ADMIN, CAP_SYS_CHROOT, CAP_SYS_NICE, CAP_SYS_PTRACE, | |
680 | CAP_SYS_TTY_CONFIG, CAP_SYS_RESOURCE, CAP_SYS_BOOT, | |
681 | CAP_AUDIT_WRITE, CAP_AUDIT_CONTROL. Also CAP_NET_ADMIN is | |
682 | retained if <option>--private-network</option> is specified. | |
683 | If the special value <literal>all</literal> is passed, all | |
684 | capabilities are retained.</para></listitem> | |
685 | </varlistentry> | |
686 | ||
687 | <varlistentry> | |
688 | <term><option>--drop-capability=</option></term> | |
689 | ||
690 | <listitem><para>Specify one or more additional capabilities to | |
691 | drop for the container. This allows running the container with | |
692 | fewer capabilities than the default (see | |
693 | above).</para></listitem> | |
694 | </varlistentry> | |
695 | ||
c6c8f6e2 LP |
696 | <varlistentry> |
697 | <term><option>--kill-signal=</option></term> | |
698 | ||
699 | <listitem><para>Specify the process signal to send to the | |
700 | container's PID 1 when nspawn itself receives SIGTERM, in | |
701 | order to trigger an orderly shutdown of the | |
702 | container. Defaults to SIGRTMIN+3 if <option>--boot</option> | |
703 | is used (on systemd-compatible init systems SIGRTMIN+3 | |
b3969f73 PA |
704 | triggers an orderly shutdown). For a list of valid signals, see |
705 | <citerefentry project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem> | |
c6c8f6e2 LP |
706 | </varlistentry> |
707 | ||
798d3a52 ZJS |
708 | <varlistentry> |
709 | <term><option>--link-journal=</option></term> | |
710 | ||
711 | <listitem><para>Control whether the container's journal shall | |
712 | be made visible to the host system. If enabled, allows viewing | |
713 | the container's journal files from the host (but not vice | |
714 | versa). Takes one of <literal>no</literal>, | |
715 | <literal>host</literal>, <literal>try-host</literal>, | |
716 | <literal>guest</literal>, <literal>try-guest</literal>, | |
717 | <literal>auto</literal>. If <literal>no</literal>, the journal | |
718 | is not linked. If <literal>host</literal>, the journal files | |
719 | are stored on the host file system (beneath | |
720 | <filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>) | |
721 | and the subdirectory is bind-mounted into the container at the | |
722 | same location. If <literal>guest</literal>, the journal files | |
723 | are stored on the guest file system (beneath | |
724 | <filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>) | |
725 | and the subdirectory is symlinked into the host at the same | |
726 | location. <literal>try-host</literal> and | |
727 | <literal>try-guest</literal> do the same but do not fail if | |
2dd67817 | 728 | the host does not have persistent journaling enabled. If |
798d3a52 ZJS |
729 | <literal>auto</literal> (the default), and the right |
730 | subdirectory of <filename>/var/log/journal</filename> exists, | |
731 | it will be bind mounted into the container. If the | |
732 | subdirectory does not exist, no linking is performed. | |
733 | Effectively, booting a container once with | |
734 | <literal>guest</literal> or <literal>host</literal> will link | |
735 | the journal persistently if further on the default of | |
b09c0bba LP |
736 | <literal>auto</literal> is used.</para> |
737 | ||
738 | <para>Note that <option>--link-journal=try-guest</option> is the default if the | |
739 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para></listitem> | |
798d3a52 ZJS |
740 | </varlistentry> |
741 | ||
742 | <varlistentry> | |
743 | <term><option>-j</option></term> | |
744 | ||
745 | <listitem><para>Equivalent to | |
746 | <option>--link-journal=try-guest</option>.</para></listitem> | |
747 | </varlistentry> | |
748 | ||
749 | <varlistentry> | |
750 | <term><option>--read-only</option></term> | |
751 | ||
752 | <listitem><para>Mount the root file system read-only for the | |
753 | container.</para></listitem> | |
754 | </varlistentry> | |
755 | ||
756 | <varlistentry> | |
757 | <term><option>--bind=</option></term> | |
758 | <term><option>--bind-ro=</option></term> | |
759 | ||
86c0dd4a | 760 | <listitem><para>Bind mount a file or directory from the host into the container. Takes one of: a path |
c7a4890c LP |
761 | argument — in which case the specified path will be mounted from the host to the same path in the container, or |
762 | a colon-separated pair of paths — in which case the first specified path is the source in the host, and the | |
763 | second path is the destination in the container, or a colon-separated triple of source path, destination path | |
86c0dd4a | 764 | and mount options. The source path may optionally be prefixed with a <literal>+</literal> character. If so, the |
c7a4890c LP |
765 | source path is taken relative to the image's root directory. This permits setting up bind mounts within the |
766 | container image. The source path may be specified as empty string, in which case a temporary directory below | |
767 | the host's <filename>/var/tmp</filename> directory is used. It is automatically removed when the container is | |
768 | shut down. Mount options are comma-separated and currently, only <option>rbind</option> and | |
769 | <option>norbind</option> are allowed, controlling whether to create a recursive or a regular bind | |
770 | mount. Defaults to "rbind". Backslash escapes are interpreted, so <literal>\:</literal> may be used to embed | |
771 | colons in either path. This option may be specified multiple times for creating multiple independent bind | |
772 | mount points. The <option>--bind-ro=</option> option creates read-only bind mounts.</para></listitem> | |
798d3a52 ZJS |
773 | </varlistentry> |
774 | ||
775 | <varlistentry> | |
776 | <term><option>--tmpfs=</option></term> | |
777 | ||
778 | <listitem><para>Mount a tmpfs file system into the container. | |
779 | Takes a single absolute path argument that specifies where to | |
780 | mount the tmpfs instance to (in which case the directory | |
781 | access mode will be chosen as 0755, owned by root/root), or | |
782 | optionally a colon-separated pair of path and mount option | |
b938cb90 | 783 | string that is used for mounting (in which case the kernel |
798d3a52 ZJS |
784 | default for access mode and owner will be chosen, unless |
785 | otherwise specified). This option is particularly useful for | |
786 | mounting directories such as <filename>/var</filename> as | |
787 | tmpfs, to allow state-less systems, in particular when | |
ffcd3e89 | 788 | combined with <option>--read-only</option>. |
b938cb90 | 789 | Backslash escapes are interpreted in the path, so |
ffcd3e89 RM |
790 | <literal>\:</literal> may be used to embed colons in the path. |
791 | </para></listitem> | |
798d3a52 ZJS |
792 | </varlistentry> |
793 | ||
5a8af538 LP |
794 | <varlistentry> |
795 | <term><option>--overlay=</option></term> | |
796 | <term><option>--overlay-ro=</option></term> | |
797 | ||
798 | <listitem><para>Combine multiple directory trees into one | |
799 | overlay file system and mount it into the container. Takes a | |
800 | list of colon-separated paths to the directory trees to | |
801 | combine and the destination mount point.</para> | |
802 | ||
2eadf91c RM |
803 | <para>Backslash escapes are interpreted in the paths, so |
804 | <literal>\:</literal> may be used to embed colons in the paths. | |
805 | </para> | |
806 | ||
5a8af538 LP |
807 | <para>If three or more paths are specified, then the last |
808 | specified path is the destination mount point in the | |
809 | container, all paths specified before refer to directory trees | |
810 | on the host and are combined in the specified order into one | |
811 | overlay file system. The left-most path is hence the lowest | |
812 | directory tree, the second-to-last path the highest directory | |
813 | tree in the stacking order. If <option>--overlay-ro=</option> | |
b938cb90 | 814 | is used instead of <option>--overlay=</option>, a read-only |
5a8af538 | 815 | overlay file system is created. If a writable overlay file |
b938cb90 | 816 | system is created, all changes made to it are written to the |
5a8af538 LP |
817 | highest directory tree in the stacking order, i.e. the |
818 | second-to-last specified.</para> | |
819 | ||
820 | <para>If only two paths are specified, then the second | |
821 | specified path is used both as the top-level directory tree in | |
822 | the stacking order as seen from the host, as well as the mount | |
823 | point for the overlay file system in the container. At least | |
824 | two paths have to be specified.</para> | |
825 | ||
86c0dd4a | 826 | <para>The source paths may optionally be prefixed with <literal>+</literal> character. If so they are taken |
c7a4890c LP |
827 | relative to the image's root directory. The uppermost source path may also be specified as empty string, in |
828 | which case a temporary directory below the host's <filename>/var/tmp</filename> is used. The directory is | |
829 | removed automatically when the container is shut down. This behaviour is useful in order to make read-only | |
830 | container directories writable while the container is running. For example, use the | |
831 | <literal>--overlay=+/var::/var</literal> option in order to automatically overlay a writable temporary | |
832 | directory on a read-only <filename>/var</filename> directory.</para> | |
86c0dd4a | 833 | |
5a8af538 LP |
834 | <para>For details about overlay file systems, see <ulink |
835 | url="https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt">overlayfs.txt</ulink>. Note | |
836 | that the semantics of overlay file systems are substantially | |
837 | different from normal file systems, in particular regarding | |
838 | reported device and inode information. Device and inode | |
839 | information may change for a file while it is being written | |
840 | to, and processes might see out-of-date versions of files at | |
841 | times. Note that this switch automatically derives the | |
842 | <literal>workdir=</literal> mount option for the overlay file | |
843 | system from the top-level directory tree, making it a sibling | |
844 | of it. It is hence essential that the top-level directory tree | |
845 | is not a mount point itself (since the working directory must | |
846 | be on the same file system as the top-most directory | |
847 | tree). Also note that the <literal>lowerdir=</literal> mount | |
848 | option receives the paths to stack in the opposite order of | |
849 | this switch.</para></listitem> | |
850 | </varlistentry> | |
851 | ||
798d3a52 | 852 | <varlistentry> |
a5f1cb3b ZJS |
853 | <term><option>-E <replaceable>NAME</replaceable>=<replaceable>VALUE</replaceable></option></term> |
854 | <term><option>--setenv=<replaceable>NAME</replaceable>=<replaceable>VALUE</replaceable></option></term> | |
798d3a52 ZJS |
855 | |
856 | <listitem><para>Specifies an environment variable assignment | |
857 | to pass to the init process in the container, in the format | |
858 | <literal>NAME=VALUE</literal>. This may be used to override | |
859 | the default variables or to set additional variables. This | |
860 | parameter may be used more than once.</para></listitem> | |
861 | </varlistentry> | |
862 | ||
798d3a52 ZJS |
863 | <varlistentry> |
864 | <term><option>--register=</option></term> | |
865 | ||
866 | <listitem><para>Controls whether the container is registered | |
867 | with | |
868 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. | |
a8eaaee7 | 869 | Takes a boolean argument, which defaults to <literal>yes</literal>. |
798d3a52 ZJS |
870 | This option should be enabled when the container runs a full |
871 | Operating System (more specifically: an init system), and is | |
872 | useful to ensure that the container is accessible via | |
873 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
874 | and shown by tools such as | |
875 | <citerefentry project='man-pages'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>. | |
876 | If the container does not run an init system, it is | |
a6b5216c | 877 | recommended to set this option to <literal>no</literal>.</para></listitem> |
798d3a52 ZJS |
878 | </varlistentry> |
879 | ||
880 | <varlistentry> | |
881 | <term><option>--keep-unit</option></term> | |
882 | ||
883 | <listitem><para>Instead of creating a transient scope unit to | |
884 | run the container in, simply register the service or scope | |
885 | unit <command>systemd-nspawn</command> has been invoked in | |
886 | with | |
887 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. | |
888 | This has no effect if <option>--register=no</option> is used. | |
889 | This switch should be used if | |
890 | <command>systemd-nspawn</command> is invoked from within a | |
891 | service unit, and the service unit's sole purpose is to run a | |
892 | single <command>systemd-nspawn</command> container. This | |
893 | option is not available if run from a user | |
894 | session.</para></listitem> | |
895 | </varlistentry> | |
896 | ||
897 | <varlistentry> | |
898 | <term><option>--personality=</option></term> | |
899 | ||
900 | <listitem><para>Control the architecture ("personality") | |
901 | reported by | |
3ba3a79d | 902 | <citerefentry project='man-pages'><refentrytitle>uname</refentrytitle><manvolnum>2</manvolnum></citerefentry> |
798d3a52 ZJS |
903 | in the container. Currently, only <literal>x86</literal> and |
904 | <literal>x86-64</literal> are supported. This is useful when | |
905 | running a 32-bit container on a 64-bit host. If this setting | |
906 | is not used, the personality reported in the container is the | |
907 | same as the one reported on the host.</para></listitem> | |
908 | </varlistentry> | |
909 | ||
910 | <varlistentry> | |
911 | <term><option>-q</option></term> | |
912 | <term><option>--quiet</option></term> | |
913 | ||
914 | <listitem><para>Turns off any status output by the tool | |
915 | itself. When this switch is used, the only output from nspawn | |
916 | will be the console output of the container OS | |
917 | itself.</para></listitem> | |
918 | </varlistentry> | |
919 | ||
920 | <varlistentry> | |
f757855e LP |
921 | <term><option>--volatile</option></term> |
922 | <term><option>--volatile=</option><replaceable>MODE</replaceable></term> | |
798d3a52 ZJS |
923 | |
924 | <listitem><para>Boots the container in volatile mode. When no | |
925 | mode parameter is passed or when mode is specified as | |
b938cb90 | 926 | <option>yes</option>, full volatile mode is enabled. This |
a8eaaee7 | 927 | means the root directory is mounted as a mostly unpopulated |
798d3a52 | 928 | <literal>tmpfs</literal> instance, and |
cd72d204 JE |
929 | <filename>/usr</filename> from the OS tree is mounted into it |
930 | in read-only mode (the system thus starts up with read-only OS | |
5164c3b4 ZJS |
931 | image, but pristine state and configuration, any changes |
932 | are lost on shutdown). When the mode parameter | |
b938cb90 | 933 | is specified as <option>state</option>, the OS tree is |
798d3a52 | 934 | mounted read-only, but <filename>/var</filename> is mounted as |
a8eaaee7 | 935 | a <literal>tmpfs</literal> instance into it (the system thus |
798d3a52 | 936 | starts up with read-only OS resources and configuration, but |
a8eaaee7 | 937 | pristine state, and any changes to the latter are lost on |
798d3a52 | 938 | shutdown). When the mode parameter is specified as |
b938cb90 | 939 | <option>no</option> (the default), the whole OS tree is made |
798d3a52 ZJS |
940 | available writable.</para> |
941 | ||
91214a37 LP |
942 | <para>This option provides similar functionality for containers as the <literal>systemd.volatile=</literal> |
943 | kernel command line switch provides for host systems. See | |
944 | <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for | |
945 | details.</para> | |
946 | ||
947 | <para>Note that enabling this setting will only work correctly with operating systems in the container that can | |
948 | boot up with only <filename>/usr</filename> mounted, and are able to automatically populate | |
949 | <filename>/var</filename>, and also <filename>/etc</filename> in case of | |
950 | <literal>--volatile=yes</literal>.</para></listitem> | |
798d3a52 ZJS |
951 | </varlistentry> |
952 | ||
f757855e LP |
953 | <varlistentry> |
954 | <term><option>--settings=</option><replaceable>MODE</replaceable></term> | |
955 | ||
956 | <listitem><para>Controls whether | |
957 | <command>systemd-nspawn</command> shall search for and use | |
958 | additional per-container settings from | |
959 | <filename>.nspawn</filename> files. Takes a boolean or the | |
960 | special values <option>override</option> or | |
961 | <option>trusted</option>.</para> | |
962 | ||
b938cb90 | 963 | <para>If enabled (the default), a settings file named after the |
f757855e LP |
964 | machine (as specified with the <option>--machine=</option> |
965 | setting, or derived from the directory or image file name) | |
966 | with the suffix <filename>.nspawn</filename> is searched in | |
967 | <filename>/etc/systemd/nspawn/</filename> and | |
968 | <filename>/run/systemd/nspawn/</filename>. If it is found | |
969 | there, its settings are read and used. If it is not found | |
b938cb90 | 970 | there, it is subsequently searched in the same directory as the |
f757855e | 971 | image file or in the immediate parent of the root directory of |
b938cb90 | 972 | the container. In this case, if the file is found, its settings |
f757855e | 973 | will be also read and used, but potentially unsafe settings |
b938cb90 | 974 | are ignored. Note that in both these cases, settings on the |
4f76ef04 | 975 | command line take precedence over the corresponding settings |
f757855e LP |
976 | from loaded <filename>.nspawn</filename> files, if both are |
977 | specified. Unsafe settings are considered all settings that | |
978 | elevate the container's privileges or grant access to | |
979 | additional resources such as files or directories of the | |
980 | host. For details about the format and contents of | |
b938cb90 | 981 | <filename>.nspawn</filename> files, consult |
f757855e LP |
982 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> |
983 | ||
b938cb90 JE |
984 | <para>If this option is set to <option>override</option>, the |
985 | file is searched, read and used the same way, however, the order of | |
f757855e LP |
986 | precedence is reversed: settings read from the |
987 | <filename>.nspawn</filename> file will take precedence over | |
988 | the corresponding command line options, if both are | |
989 | specified.</para> | |
990 | ||
b938cb90 | 991 | <para>If this option is set to <option>trusted</option>, the |
f757855e | 992 | file is searched, read and used the same way, but regardless |
a8eaaee7 | 993 | of being found in <filename>/etc/systemd/nspawn/</filename>, |
f757855e LP |
994 | <filename>/run/systemd/nspawn/</filename> or next to the image |
995 | file or container root directory, all settings will take | |
b938cb90 | 996 | effect, however, command line arguments still take precedence |
f757855e LP |
997 | over corresponding settings.</para> |
998 | ||
b938cb90 | 999 | <para>If disabled, no <filename>.nspawn</filename> file is read |
f757855e LP |
1000 | and no settings except the ones on the command line are in |
1001 | effect.</para></listitem> | |
1002 | </varlistentry> | |
1003 | ||
9c1e04d0 | 1004 | <varlistentry> |
b09c0bba | 1005 | <term><option>--notify-ready=</option></term> |
9c1e04d0 AP |
1006 | |
1007 | <listitem><para>Configures support for notifications from the container's init process. | |
b09c0bba | 1008 | <option>--notify-ready=</option> takes a boolean (<option>no</option> and <option>yes</option>). |
9c1e04d0 AP |
1009 | With option <option>no</option> systemd-nspawn notifies systemd |
1010 | with a <literal>READY=1</literal> message when the init process is created. | |
1011 | With option <option>yes</option> systemd-nspawn waits for the | |
1012 | <literal>READY=1</literal> message from the init process in the container | |
1013 | before sending its own to systemd. For more details about notifications | |
1014 | see <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>).</para></listitem> | |
1015 | </varlistentry> | |
1016 | ||
798d3a52 ZJS |
1017 | <xi:include href="standard-options.xml" xpointer="help" /> |
1018 | <xi:include href="standard-options.xml" xpointer="version" /> | |
1019 | </variablelist> | |
1020 | ||
1021 | </refsect1> | |
1022 | ||
1023 | <refsect1> | |
1024 | <title>Examples</title> | |
1025 | ||
1026 | <example> | |
1027 | <title>Download a Fedora image and start a shell in it</title> | |
1028 | ||
96ee6ce3 SS |
1029 | <programlisting># machinectl pull-raw --verify=no http://ftp.halifax.rwth-aachen.de/fedora/linux/releases/24/CloudImages/x86_64/images/Fedora-Cloud-Base-24-1.2.x86_64.raw.xz |
1030 | # systemd-nspawn -M Fedora-Cloud-Base-24-1.2.x86_64.raw</programlisting> | |
e0ea94c1 | 1031 | |
798d3a52 ZJS |
1032 | <para>This downloads an image using |
1033 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
1034 | and opens a shell in it.</para> | |
1035 | </example> | |
e0ea94c1 | 1036 | |
798d3a52 ZJS |
1037 | <example> |
1038 | <title>Build and boot a minimal Fedora distribution in a container</title> | |
8f7a3c14 | 1039 | |
09c76ef6 | 1040 | <programlisting># dnf -y --releasever=23 --installroot=/srv/mycontainer --disablerepo='*' --enablerepo=fedora --enablerepo=updates install systemd passwd dnf fedora-release vim-minimal |
2b3987a8 | 1041 | # systemd-nspawn -bD /srv/mycontainer</programlisting> |
8f7a3c14 | 1042 | |
798d3a52 ZJS |
1043 | <para>This installs a minimal Fedora distribution into the |
1044 | directory <filename noindex='true'>/srv/mycontainer/</filename> | |
1045 | and then boots an OS in a namespace container in it.</para> | |
1046 | </example> | |
8f7a3c14 | 1047 | |
798d3a52 ZJS |
1048 | <example> |
1049 | <title>Spawn a shell in a container of a minimal Debian unstable distribution</title> | |
8f7a3c14 | 1050 | |
798d3a52 | 1051 | <programlisting># debootstrap --arch=amd64 unstable ~/debian-tree/ |
25f5971b | 1052 | # systemd-nspawn -D ~/debian-tree/</programlisting> |
8f7a3c14 | 1053 | |
798d3a52 ZJS |
1054 | <para>This installs a minimal Debian unstable distribution into |
1055 | the directory <filename>~/debian-tree/</filename> and then | |
1056 | spawns a shell in a namespace container in it.</para> | |
1057 | </example> | |
8f7a3c14 | 1058 | |
798d3a52 ZJS |
1059 | <example> |
1060 | <title>Boot a minimal Arch Linux distribution in a container</title> | |
68562936 | 1061 | |
798d3a52 | 1062 | <programlisting># pacstrap -c -d ~/arch-tree/ base |
68562936 WG |
1063 | # systemd-nspawn -bD ~/arch-tree/</programlisting> |
1064 | ||
ff9b60f3 | 1065 | <para>This installs a minimal Arch Linux distribution into the |
798d3a52 ZJS |
1066 | directory <filename>~/arch-tree/</filename> and then boots an OS |
1067 | in a namespace container in it.</para> | |
1068 | </example> | |
68562936 | 1069 | |
798d3a52 | 1070 | <example> |
17cbb288 | 1071 | <title>Boot into an ephemeral snapshot of the host system</title> |
f9f4dd51 | 1072 | |
798d3a52 | 1073 | <programlisting># systemd-nspawn -D / -xb</programlisting> |
f9f4dd51 | 1074 | |
17cbb288 LP |
1075 | <para>This runs a copy of the host system in a snapshot which is removed immediately when the container |
1076 | exits. All file system changes made during runtime will be lost on shutdown, hence.</para> | |
798d3a52 | 1077 | </example> |
f9f4dd51 | 1078 | |
798d3a52 ZJS |
1079 | <example> |
1080 | <title>Run a container with SELinux sandbox security contexts</title> | |
a8828ed9 | 1081 | |
798d3a52 | 1082 | <programlisting># chcon system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -R /srv/container |
a8828ed9 | 1083 | # 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</programlisting> |
798d3a52 ZJS |
1084 | </example> |
1085 | </refsect1> | |
1086 | ||
1087 | <refsect1> | |
1088 | <title>Exit status</title> | |
1089 | ||
1090 | <para>The exit code of the program executed in the container is | |
1091 | returned.</para> | |
1092 | </refsect1> | |
1093 | ||
1094 | <refsect1> | |
1095 | <title>See Also</title> | |
1096 | <para> | |
1097 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
f757855e | 1098 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
798d3a52 ZJS |
1099 | <citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
1100 | <citerefentry project='mankier'><refentrytitle>dnf</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
798d3a52 ZJS |
1101 | <citerefentry project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>, |
1102 | <citerefentry project='archlinux'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
1103 | <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
1104 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
3ba3a79d | 1105 | <citerefentry project='man-pages'><refentrytitle>btrfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> |
798d3a52 ZJS |
1106 | </para> |
1107 | </refsect1> | |
8f7a3c14 LP |
1108 | |
1109 | </refentry> |