]>
Commit | Line | Data |
---|---|---|
6e866b33 | 1 | <?xml version='1.0'?> |
bb4f798a | 2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
b012e921 MB |
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ |
4 | <!ENTITY fedora_latest_version "28"> | |
5 | <!ENTITY fedora_cloud_release "1.1"> | |
6 | ]> | |
bb4f798a | 7 | <!-- SPDX-License-Identifier: LGPL-2.1+ --> |
663996b3 | 8 | |
60f067b4 | 9 | <refentry id="systemd-nspawn" |
e735f4d4 MP |
10 | xmlns:xi="http://www.w3.org/2001/XInclude"> |
11 | ||
12 | <refentryinfo> | |
13 | <title>systemd-nspawn</title> | |
14 | <productname>systemd</productname> | |
e735f4d4 MP |
15 | </refentryinfo> |
16 | ||
17 | <refmeta> | |
18 | <refentrytitle>systemd-nspawn</refentrytitle> | |
19 | <manvolnum>1</manvolnum> | |
20 | </refmeta> | |
21 | ||
22 | <refnamediv> | |
23 | <refname>systemd-nspawn</refname> | |
6e866b33 | 24 | <refpurpose>Spawn a command or OS in a light-weight container</refpurpose> |
e735f4d4 MP |
25 | </refnamediv> |
26 | ||
27 | <refsynopsisdiv> | |
28 | <cmdsynopsis> | |
29 | <command>systemd-nspawn</command> | |
30 | <arg choice="opt" rep="repeat">OPTIONS</arg> | |
31 | <arg choice="opt"><replaceable>COMMAND</replaceable> | |
32 | <arg choice="opt" rep="repeat">ARGS</arg> | |
33 | </arg> | |
34 | </cmdsynopsis> | |
35 | <cmdsynopsis> | |
36 | <command>systemd-nspawn</command> | |
aa27b158 | 37 | <arg choice="plain">--boot</arg> |
e735f4d4 MP |
38 | <arg choice="opt" rep="repeat">OPTIONS</arg> |
39 | <arg choice="opt" rep="repeat">ARGS</arg> | |
40 | </cmdsynopsis> | |
41 | </refsynopsisdiv> | |
42 | ||
43 | <refsect1> | |
44 | <title>Description</title> | |
45 | ||
5a920b42 MP |
46 | <para><command>systemd-nspawn</command> may be used to run a command or OS in a light-weight namespace |
47 | container. In many ways it is similar to <citerefentry | |
48 | project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, but more powerful | |
49 | since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and | |
50 | the host and domain name.</para> | |
51 | ||
52 | <para><command>systemd-nspawn</command> may be invoked on any directory tree containing an operating system tree, | |
53 | using the <option>--directory=</option> command line option. By using the <option>--machine=</option> option an OS | |
54 | tree is automatically searched for in a couple of locations, most importantly in | |
6e866b33 | 55 | <filename>/var/lib/machines</filename>, the suggested directory to place OS container images installed on the |
5a920b42 MP |
56 | system.</para> |
57 | ||
58 | <para>In contrast to <citerefentry | |
59 | project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>systemd-nspawn</command> | |
60 | may be used to boot full Linux-based operating systems in a container.</para> | |
61 | ||
62 | <para><command>systemd-nspawn</command> limits access to various kernel interfaces in the container to read-only, | |
63 | such as <filename>/sys</filename>, <filename>/proc/sys</filename> or <filename>/sys/fs/selinux</filename>. The | |
64 | host's network interfaces and the system clock may not be changed from within the container. Device nodes may not | |
65 | be created. The host system cannot be rebooted and kernel modules may not be loaded from within the | |
e735f4d4 MP |
66 | container.</para> |
67 | ||
5a920b42 MP |
68 | <para>Use a tool like <citerefentry |
69 | project='mankier'><refentrytitle>dnf</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry | |
70 | project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>, or | |
71 | <citerefentry project='archlinux'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry> to | |
72 | set up an OS directory tree suitable as file system hierarchy for <command>systemd-nspawn</command> containers. See | |
73 | the Examples section below for details on suitable invocation of these commands.</para> | |
74 | ||
75 | <para>As a safety check <command>systemd-nspawn</command> will verify the existence of | |
76 | <filename>/usr/lib/os-release</filename> or <filename>/etc/os-release</filename> in the container tree before | |
77 | starting the container (see | |
78 | <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry>). It might be | |
79 | necessary to add this file to the container tree manually if the OS of the container is too old to contain this | |
e735f4d4 | 80 | file out-of-the-box.</para> |
5a920b42 MP |
81 | |
82 | <para><command>systemd-nspawn</command> may be invoked directly from the interactive command line or run as system | |
83 | service in the background. In this mode each container instance runs as its own service instance; a default | |
84 | template unit file <filename>systemd-nspawn@.service</filename> is provided to make this easy, taking the container | |
85 | name as instance identifier. Note that different default options apply when <command>systemd-nspawn</command> is | |
86 | invoked by the template unit file than interactively on the command line. Most importantly the template unit file | |
87 | makes use of the <option>--boot</option> which is not the default in case <command>systemd-nspawn</command> is | |
88 | invoked from the interactive command line. Further differences with the defaults are documented along with the | |
89 | various supported options below.</para> | |
90 | ||
91 | <para>The <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> tool may | |
92 | be used to execute a number of operations on containers. In particular it provides easy-to-use commands to run | |
93 | containers as system services using the <filename>systemd-nspawn@.service</filename> template unit | |
94 | file.</para> | |
95 | ||
96 | <para>Along with each container a settings file with the <filename>.nspawn</filename> suffix may exist, containing | |
97 | additional settings to apply when running the container. See | |
98 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry> for | |
99 | details. Settings files override the default options used by the <filename>systemd-nspawn@.service</filename> | |
100 | template unit file, making it usually unnecessary to alter this template file directly.</para> | |
101 | ||
102 | <para>Note that <command>systemd-nspawn</command> will mount file systems private to the container to | |
103 | <filename>/dev</filename>, <filename>/run</filename> and similar. These will not be visible outside of the | |
104 | container, and their contents will be lost when the container exits.</para> | |
105 | ||
106 | <para>Note that running two <command>systemd-nspawn</command> containers from the same directory tree will not make | |
107 | processes in them see each other. The PID namespace separation of the two containers is complete and the containers | |
108 | will share very few runtime objects except for the underlying file system. Use | |
109 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s | |
110 | <command>login</command> or <command>shell</command> commands to request an additional login session in a running | |
111 | container.</para> | |
112 | ||
113 | <para><command>systemd-nspawn</command> implements the <ulink | |
2897b343 | 114 | url="https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container Interface</ulink> |
5a920b42 MP |
115 | specification.</para> |
116 | ||
117 | <para>While running, containers invoked with <command>systemd-nspawn</command> are registered with the | |
118 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry> service that | |
119 | keeps track of running containers, and provides programming interfaces to interact with them.</para> | |
e735f4d4 MP |
120 | </refsect1> |
121 | ||
122 | <refsect1> | |
123 | <title>Options</title> | |
124 | ||
125 | <para>If option <option>-b</option> is specified, the arguments | |
1d42b86d | 126 | are used as arguments for the init program. Otherwise, |
e735f4d4 MP |
127 | <replaceable>COMMAND</replaceable> specifies the program to launch |
128 | in the container, and the remaining arguments are used as | |
5a920b42 | 129 | arguments for this program. If <option>--boot</option> is not used and |
e3bff60a | 130 | no arguments are specified, a shell is launched in the |
e735f4d4 MP |
131 | container.</para> |
132 | ||
133 | <para>The following options are understood:</para> | |
134 | ||
135 | <variablelist> | |
bb4f798a MB |
136 | |
137 | <varlistentry> | |
138 | <term><option>-q</option></term> | |
139 | <term><option>--quiet</option></term> | |
140 | ||
141 | <listitem><para>Turns off any status output by the tool | |
142 | itself. When this switch is used, the only output from nspawn | |
143 | will be the console output of the container OS | |
144 | itself.</para></listitem> | |
145 | </varlistentry> | |
146 | ||
147 | <varlistentry> | |
148 | <term><option>--settings=</option><replaceable>MODE</replaceable></term> | |
149 | ||
150 | <listitem><para>Controls whether | |
151 | <command>systemd-nspawn</command> shall search for and use | |
152 | additional per-container settings from | |
153 | <filename>.nspawn</filename> files. Takes a boolean or the | |
154 | special values <option>override</option> or | |
155 | <option>trusted</option>.</para> | |
156 | ||
157 | <para>If enabled (the default), a settings file named after the | |
158 | machine (as specified with the <option>--machine=</option> | |
159 | setting, or derived from the directory or image file name) | |
160 | with the suffix <filename>.nspawn</filename> is searched in | |
161 | <filename>/etc/systemd/nspawn/</filename> and | |
162 | <filename>/run/systemd/nspawn/</filename>. If it is found | |
163 | there, its settings are read and used. If it is not found | |
164 | there, it is subsequently searched in the same directory as the | |
165 | image file or in the immediate parent of the root directory of | |
166 | the container. In this case, if the file is found, its settings | |
167 | will be also read and used, but potentially unsafe settings | |
168 | are ignored. Note that in both these cases, settings on the | |
169 | command line take precedence over the corresponding settings | |
170 | from loaded <filename>.nspawn</filename> files, if both are | |
171 | specified. Unsafe settings are considered all settings that | |
172 | elevate the container's privileges or grant access to | |
173 | additional resources such as files or directories of the | |
174 | host. For details about the format and contents of | |
175 | <filename>.nspawn</filename> files, consult | |
176 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> | |
177 | ||
178 | <para>If this option is set to <option>override</option>, the | |
179 | file is searched, read and used the same way, however, the order of | |
180 | precedence is reversed: settings read from the | |
181 | <filename>.nspawn</filename> file will take precedence over | |
182 | the corresponding command line options, if both are | |
183 | specified.</para> | |
184 | ||
185 | <para>If this option is set to <option>trusted</option>, the | |
186 | file is searched, read and used the same way, but regardless | |
187 | of being found in <filename>/etc/systemd/nspawn/</filename>, | |
188 | <filename>/run/systemd/nspawn/</filename> or next to the image | |
189 | file or container root directory, all settings will take | |
190 | effect, however, command line arguments still take precedence | |
191 | over corresponding settings.</para> | |
192 | ||
193 | <para>If disabled, no <filename>.nspawn</filename> file is read | |
194 | and no settings except the ones on the command line are in | |
195 | effect.</para></listitem> | |
196 | </varlistentry> | |
197 | ||
198 | </variablelist> | |
199 | ||
200 | <refsect2> | |
201 | <title>Image Options</title> | |
202 | ||
203 | <variablelist> | |
204 | ||
e735f4d4 MP |
205 | <varlistentry> |
206 | <term><option>-D</option></term> | |
207 | <term><option>--directory=</option></term> | |
208 | ||
209 | <listitem><para>Directory to use as file system root for the | |
210 | container.</para> | |
211 | ||
212 | <para>If neither <option>--directory=</option>, nor | |
213 | <option>--image=</option> is specified the directory is | |
13d276d0 MP |
214 | determined by searching for a directory named the same as the |
215 | machine name specified with <option>--machine=</option>. See | |
216 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
217 | section "Files and Directories" for the precise search path.</para> | |
218 | ||
219 | <para>If neither <option>--directory=</option>, | |
220 | <option>--image=</option>, nor <option>--machine=</option> | |
221 | are specified, the current directory will | |
222 | be used. May not be specified together with | |
e735f4d4 MP |
223 | <option>--image=</option>.</para></listitem> |
224 | </varlistentry> | |
225 | ||
226 | <varlistentry> | |
227 | <term><option>--template=</option></term> | |
228 | ||
bb4f798a MB |
229 | <listitem><para>Directory or <literal>btrfs</literal> subvolume to use as template for the |
230 | container's root directory. If this is specified and the container's root directory (as configured by | |
231 | <option>--directory=</option>) does not yet exist it is created as <literal>btrfs</literal> snapshot | |
232 | (if supported) or plain directory (otherwise) and populated from this template tree. Ideally, the | |
233 | specified template path refers to the root of a <literal>btrfs</literal> subvolume, in which case a | |
234 | simple copy-on-write snapshot is taken, and populating the root directory is instant. If the | |
235 | specified template path does not refer to the root of a <literal>btrfs</literal> subvolume (or not | |
236 | even to a <literal>btrfs</literal> file system at all), the tree is copied (though possibly in a | |
237 | 'reflink' copy-on-write scheme — if the file system supports that), which can be substantially more | |
238 | time-consuming. Note that the snapshot taken is of the specified directory or subvolume, including | |
239 | all subdirectories and subvolumes below it, but excluding any sub-mounts. May not be specified | |
240 | together with <option>--image=</option> or <option>--ephemeral</option>.</para> | |
e3bff60a MP |
241 | |
242 | <para>Note that this switch leaves host name, machine ID and | |
243 | all other settings that could identify the instance | |
244 | unmodified.</para></listitem> | |
e735f4d4 MP |
245 | </varlistentry> |
246 | ||
247 | <varlistentry> | |
248 | <term><option>-x</option></term> | |
249 | <term><option>--ephemeral</option></term> | |
250 | ||
2897b343 MP |
251 | <listitem><para>If specified, the container is run with a temporary snapshot of its file system that is removed |
252 | immediately when the container terminates. May not be specified together with | |
e3bff60a | 253 | <option>--template=</option>.</para> |
bb4f798a MB |
254 | <para>Note that this switch leaves host name, machine ID and all other settings that could identify |
255 | the instance unmodified. Please note that — as with <option>--template=</option> — taking the | |
256 | temporary snapshot is more efficient on file systems that support subvolume snapshots or 'reflinks' | |
257 | natively (<literal>btrfs</literal> or new <literal>xfs</literal>) than on more traditional file | |
258 | systems that do not (<literal>ext4</literal>). Note that the snapshot taken is of the specified | |
259 | directory or subvolume, including all subdirectories and subvolumes below it, but excluding any | |
260 | sub-mounts.</para> | |
261 | ||
262 | <para>With this option no modifications of the container image are retained. Use | |
263 | <option>--volatile=</option> (described below) for other mechanisms to restrict persistency of | |
264 | container images during runtime.</para> | |
265 | </listitem> | |
e735f4d4 MP |
266 | </varlistentry> |
267 | ||
268 | <varlistentry> | |
269 | <term><option>-i</option></term> | |
270 | <term><option>--image=</option></term> | |
271 | ||
272 | <listitem><para>Disk image to mount the root directory for the | |
273 | container from. Takes a path to a regular file or to a block | |
274 | device node. The file or block device must contain | |
275 | either:</para> | |
276 | ||
277 | <itemizedlist> | |
278 | <listitem><para>An MBR partition table with a single | |
279 | partition of type 0x83 that is marked | |
280 | bootable.</para></listitem> | |
281 | ||
282 | <listitem><para>A GUID partition table (GPT) with a single | |
283 | partition of type | |
284 | 0fc63daf-8483-4772-8e79-3d69d8477de4.</para></listitem> | |
285 | ||
286 | <listitem><para>A GUID partition table (GPT) with a marked | |
287 | root partition which is mounted as the root directory of the | |
288 | container. Optionally, GPT images may contain a home and/or | |
289 | a server data partition which are mounted to the appropriate | |
290 | places in the container. All these partitions must be | |
291 | identified by the partition types defined by the <ulink | |
2897b343 | 292 | url="https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/">Discoverable |
e735f4d4 | 293 | Partitions Specification</ulink>.</para></listitem> |
2897b343 MP |
294 | |
295 | <listitem><para>No partition table, and a single file system spanning the whole image.</para></listitem> | |
e735f4d4 MP |
296 | </itemizedlist> |
297 | ||
2897b343 MP |
298 | <para>On GPT images, if an EFI System Partition (ESP) is discovered, it is automatically mounted to |
299 | <filename>/efi</filename> (or <filename>/boot</filename> as fallback) in case a directory by this name exists | |
300 | and is empty.</para> | |
301 | ||
302 | <para>Partitions encrypted with LUKS are automatically decrypted. Also, on GPT images dm-verity data integrity | |
303 | hash partitions are set up if the root hash for them is specified using the <option>--root-hash=</option> | |
304 | option.</para> | |
305 | ||
306 | <para>Any other partitions, such as foreign partitions or swap partitions are not mounted. May not be specified | |
307 | together with <option>--directory=</option>, <option>--template=</option>.</para></listitem> | |
308 | </varlistentry> | |
309 | ||
bb4f798a MB |
310 | <varlistentry> |
311 | <term><option>--oci-bundle=</option></term> | |
312 | ||
313 | <listitem><para>Takes the path to an OCI runtime bundle to invoke, as specified in the <ulink | |
314 | url="https://github.com/opencontainers/runtime-spec/blob/master/spec.md">OCI Runtime Specification</ulink>. In | |
315 | this case no <filename>.nspawn</filename> file is loaded, and the root directory and various settings are read | |
316 | from the OCI runtime JSON data (but data passed on the command line takes precedence).</para></listitem> | |
317 | </varlistentry> | |
318 | ||
319 | <varlistentry> | |
320 | <term><option>--read-only</option></term> | |
321 | ||
322 | <listitem><para>Mount the container's root file system (and any other file systems container in the container | |
323 | image) read-only. This has no effect on additional mounts made with <option>--bind=</option>, | |
324 | <option>--tmpfs=</option> and similar options. This mode is implied if the container image file or directory is | |
325 | marked read-only itself. It is also implied if <option>--volatile=</option> is used. In this case the container | |
326 | image on disk is strictly read-only, while changes are permitted but kept non-persistently in memory only. For | |
327 | further details, see below.</para></listitem> | |
328 | </varlistentry> | |
329 | ||
330 | <varlistentry> | |
331 | <term><option>--volatile</option></term> | |
332 | <term><option>--volatile=</option><replaceable>MODE</replaceable></term> | |
333 | ||
334 | <listitem><para>Boots the container in volatile mode. When no mode parameter is passed or when mode is | |
335 | specified as <option>yes</option>, full volatile mode is enabled. This means the root directory is mounted as a | |
336 | mostly unpopulated <literal>tmpfs</literal> instance, and <filename>/usr/</filename> from the OS tree is | |
337 | mounted into it in read-only mode (the system thus starts up with read-only OS image, but pristine state and | |
338 | configuration, any changes are lost on shutdown). When the mode parameter is specified as | |
339 | <option>state</option>, the OS tree is mounted read-only, but <filename>/var/</filename> is mounted as a | |
340 | writable <literal>tmpfs</literal> instance into it (the system thus starts up with read-only OS resources and | |
341 | configuration, but pristine state, and any changes to the latter are lost on shutdown). When the mode parameter | |
342 | is specified as <option>overlay</option> the read-only root file system is combined with a writable | |
343 | <filename>tmpfs</filename> instance through <literal>overlayfs</literal>, so that it appears at it normally | |
344 | would, but any changes are applied to the temporary file system only and lost when the container is | |
345 | terminated. When the mode parameter is specified as <option>no</option> (the default), the whole OS tree is | |
346 | made available writable (unless <option>--read-only</option> is specified, see above).</para> | |
347 | ||
348 | <para>Note that if one of the volatile modes is chosen, its effect is limited to the root file system (or | |
349 | <filename>/var/</filename> in case of <option>state</option>), and any other mounts placed in the hierarchy are | |
350 | unaffected — regardless if they are established automatically (e.g. the EFI system partition that might be | |
351 | mounted to <filename>/efi/</filename> or <filename>/boot/</filename>) or explicitly (e.g. through an additional | |
352 | command line option such as <option>--bind=</option>, see below). This means, even if | |
353 | <option>--volatile=overlay</option> is used changes to <filename>/efi/</filename> or | |
354 | <filename>/boot/</filename> are prohibited in case such a partition exists in the container image operated on, | |
355 | and even if <option>--volatile=state</option> is used the hypothetical file <filename>/etc/foobar</filename> is | |
356 | potentially writable if <option>--bind=/etc/foobar</option> if used to mount it from outside the read-only | |
357 | container <filename>/etc</filename> directory.</para> | |
358 | ||
359 | <para>The <option>--ephemeral</option> option is closely related to this setting, and provides similar | |
360 | behaviour by making a temporary, ephemeral copy of the whole OS image and executing that. For further details, | |
361 | see above.</para> | |
362 | ||
363 | <para>The <option>--tmpfs=</option> and <option>--overlay=</option> options provide similar functionality, but | |
364 | for specific sub-directories of the OS image only. For details, see below.</para> | |
365 | ||
366 | <para>This option provides similar functionality for containers as the <literal>systemd.volatile=</literal> | |
367 | kernel command line switch provides for host systems. See | |
368 | <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for | |
369 | details.</para> | |
370 | ||
371 | <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work correctly | |
372 | with operating systems in the container that can boot up with only <filename>/usr</filename> mounted, and are | |
373 | able to automatically populate <filename>/var</filename>, and also <filename>/etc</filename> in case of | |
374 | <literal>--volatile=yes</literal>. The <option>overlay</option> option does not require any particular | |
375 | preparations in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file | |
376 | systems in a number of ways, and hence compatibility is limited.</para></listitem> | |
377 | </varlistentry> | |
378 | ||
2897b343 MP |
379 | <varlistentry> |
380 | <term><option>--root-hash=</option></term> | |
381 | ||
382 | <listitem><para>Takes a data integrity (dm-verity) root hash specified in hexadecimal. This option enables data | |
383 | integrity checks using dm-verity, if the used image contains the appropriate integrity data (see above). The | |
384 | specified hash must match the root hash of integrity data, and is usually at least 256 bits (and hence 64 | |
385 | formatted hexadecimal characters) long (in case of SHA256 for example). If this option is not specified, but | |
386 | the image file carries the <literal>user.verity.roothash</literal> extended file attribute (see <citerefentry | |
387 | project='man-pages'><refentrytitle>xattr</refentrytitle><manvolnum>7</manvolnum></citerefentry>), then the root | |
388 | hash is read from it, also as formatted hexadecimal characters. If the extended file attribute is not found (or | |
389 | is not supported by the underlying file system), but a file with the <filename>.roothash</filename> suffix is | |
390 | found next to the image file, bearing otherwise the same name, the root hash is read from it and automatically | |
391 | used, also as formatted hexadecimal characters.</para></listitem> | |
e735f4d4 MP |
392 | </varlistentry> |
393 | ||
bb4f798a MB |
394 | <varlistentry> |
395 | <term><option>--pivot-root=</option></term> | |
396 | ||
397 | <listitem><para>Pivot the specified directory to <filename>/</filename> inside the container, and either unmount the | |
398 | container's old root, or pivot it to another specified directory. Takes one of: a path argument — in which case the | |
399 | specified path will be pivoted to <filename>/</filename> and the old root will be unmounted; or a colon-separated pair | |
400 | of new root path and pivot destination for the old root. The new root path will be pivoted to <filename>/</filename>, | |
401 | and the old <filename>/</filename> will be pivoted to the other directory. Both paths must be absolute, and are resolved | |
402 | in the container's file system namespace.</para> | |
403 | ||
404 | <para>This is for containers which have several bootable directories in them; for example, several | |
405 | <ulink url="https://ostree.readthedocs.io/en/latest/">OSTree</ulink> deployments. It emulates the behavior of | |
406 | the boot loader and initial RAM disk which normally select which directory to mount as the root and start the | |
407 | container's PID 1 in.</para></listitem> | |
408 | </varlistentry> | |
409 | </variablelist> | |
410 | ||
411 | </refsect2><refsect2> | |
412 | <title>Execution Options</title> | |
413 | ||
414 | <variablelist> | |
4c89c718 MP |
415 | <varlistentry> |
416 | <term><option>-a</option></term> | |
417 | <term><option>--as-pid2</option></term> | |
418 | ||
419 | <listitem><para>Invoke the shell or specified program as process ID (PID) 2 instead of PID 1 (init). By | |
1d42b86d MB |
420 | default, if neither this option nor <option>--boot</option> is used, the selected program is run as the process |
421 | with PID 1, a mode only suitable for programs that are aware of the special semantics that the process with | |
422 | PID 1 has on UNIX. For example, it needs to reap all processes reparented to it, and should implement | |
4c89c718 MP |
423 | <command>sysvinit</command> compatible signal handling (specifically: it needs to reboot on SIGINT, reexecute |
424 | on SIGTERM, reload configuration on SIGHUP, and so on). With <option>--as-pid2</option> a minimal stub init | |
1d42b86d | 425 | process is run as PID 1 and the selected program is executed as PID 2 (and hence does not need to implement any |
4c89c718 MP |
426 | special semantics). The stub init process will reap processes as necessary and react appropriately to |
427 | signals. It is recommended to use this mode to invoke arbitrary commands in containers, unless they have been | |
428 | modified to run correctly as PID 1. Or in other words: this switch should be used for pretty much all commands, | |
429 | except when the command refers to an init or shell implementation, as these are generally capable of running | |
8a584da2 | 430 | correctly as PID 1. This option may not be combined with <option>--boot</option>.</para> |
4c89c718 MP |
431 | </listitem> |
432 | </varlistentry> | |
433 | ||
e735f4d4 MP |
434 | <varlistentry> |
435 | <term><option>-b</option></term> | |
436 | <term><option>--boot</option></term> | |
437 | ||
1d42b86d | 438 | <listitem><para>Automatically search for an init program and invoke it as PID 1, instead of a shell or a user |
4c89c718 | 439 | supplied program. If this option is used, arguments specified on the command line are used as arguments for the |
1d42b86d | 440 | init program. This option may not be combined with <option>--as-pid2</option>.</para> |
4c89c718 MP |
441 | |
442 | <para>The following table explains the different modes of invocation and relationship to | |
443 | <option>--as-pid2</option> (see above):</para> | |
444 | ||
445 | <table> | |
446 | <title>Invocation Mode</title> | |
447 | <tgroup cols='2' align='left' colsep='1' rowsep='1'> | |
448 | <colspec colname="switch" /> | |
449 | <colspec colname="explanation" /> | |
450 | <thead> | |
451 | <row> | |
452 | <entry>Switch</entry> | |
453 | <entry>Explanation</entry> | |
454 | </row> | |
455 | </thead> | |
456 | <tbody> | |
457 | <row> | |
458 | <entry>Neither <option>--as-pid2</option> nor <option>--boot</option> specified</entry> | |
aa27b158 | 459 | <entry>The passed parameters are interpreted as the command line, which is executed as PID 1 in the container.</entry> |
4c89c718 MP |
460 | </row> |
461 | ||
462 | <row> | |
463 | <entry><option>--as-pid2</option> specified</entry> | |
aa27b158 | 464 | <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> |
4c89c718 MP |
465 | </row> |
466 | ||
467 | <row> | |
468 | <entry><option>--boot</option> specified</entry> | |
1d42b86d | 469 | <entry>An init program is automatically searched for and run as PID 1 in the container. The passed parameters are used as invocation parameters for this process.</entry> |
4c89c718 MP |
470 | </row> |
471 | ||
472 | </tbody> | |
473 | </tgroup> | |
474 | </table> | |
5a920b42 MP |
475 | |
476 | <para>Note that <option>--boot</option> is the default mode of operation if the | |
477 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
4c89c718 MP |
478 | </listitem> |
479 | </varlistentry> | |
480 | ||
481 | <varlistentry> | |
482 | <term><option>--chdir=</option></term> | |
483 | ||
484 | <listitem><para>Change to the specified working directory before invoking the process in the container. Expects | |
485 | an absolute path in the container's file system namespace.</para></listitem> | |
e735f4d4 MP |
486 | </varlistentry> |
487 | ||
2897b343 | 488 | <varlistentry> |
bb4f798a MB |
489 | <term><option>-E <replaceable>NAME</replaceable>=<replaceable>VALUE</replaceable></option></term> |
490 | <term><option>--setenv=<replaceable>NAME</replaceable>=<replaceable>VALUE</replaceable></option></term> | |
2897b343 | 491 | |
bb4f798a MB |
492 | <listitem><para>Specifies an environment variable assignment |
493 | to pass to the init process in the container, in the format | |
494 | <literal>NAME=VALUE</literal>. This may be used to override | |
495 | the default variables or to set additional variables. This | |
496 | parameter may be used more than once.</para></listitem> | |
2897b343 MP |
497 | </varlistentry> |
498 | ||
e735f4d4 MP |
499 | <varlistentry> |
500 | <term><option>-u</option></term> | |
501 | <term><option>--user=</option></term> | |
502 | ||
503 | <listitem><para>After transitioning into the container, change | |
504 | to the specified user-defined in the container's user | |
505 | database. Like all other systemd-nspawn features, this is not | |
506 | a security feature and provides protection against accidental | |
507 | destructive operations only.</para></listitem> | |
508 | </varlistentry> | |
509 | ||
bb4f798a MB |
510 | <varlistentry> |
511 | <term><option>--kill-signal=</option></term> | |
512 | ||
513 | <listitem><para>Specify the process signal to send to the container's PID 1 when nspawn itself receives | |
514 | <constant>SIGTERM</constant>, in order to trigger an orderly shutdown of the container. Defaults to | |
515 | <constant>SIGRTMIN+3</constant> if <option>--boot</option> is used (on systemd-compatible init systems | |
516 | <constant>SIGRTMIN+3</constant> triggers an orderly shutdown). If <option>--boot</option> is not used and this | |
517 | option is not specified the container's processes are terminated abruptly via <constant>SIGKILL</constant>. For | |
518 | a list of valid signals, see <citerefentry | |
519 | project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem> | |
520 | </varlistentry> | |
521 | ||
522 | <varlistentry> | |
523 | <term><option>--notify-ready=</option></term> | |
524 | ||
525 | <listitem><para>Configures support for notifications from the container's init process. | |
526 | <option>--notify-ready=</option> takes a boolean (<option>no</option> and <option>yes</option>). | |
527 | With option <option>no</option> systemd-nspawn notifies systemd | |
528 | with a <literal>READY=1</literal> message when the init process is created. | |
529 | With option <option>yes</option> systemd-nspawn waits for the | |
530 | <literal>READY=1</literal> message from the init process in the container | |
531 | before sending its own to systemd. For more details about notifications | |
532 | see <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>).</para></listitem> | |
533 | </varlistentry> | |
534 | </variablelist> | |
535 | ||
536 | </refsect2><refsect2> | |
537 | <title>System Identity Options</title> | |
538 | ||
539 | <variablelist> | |
e735f4d4 MP |
540 | <varlistentry> |
541 | <term><option>-M</option></term> | |
542 | <term><option>--machine=</option></term> | |
543 | ||
544 | <listitem><para>Sets the machine name for this container. This | |
545 | name may be used to identify this container during its runtime | |
546 | (for example in tools like | |
547 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
548 | and similar), and is used to initialize the container's | |
549 | hostname (which the container can choose to override, | |
550 | however). If not specified, the last component of the root | |
551 | directory path of the container is used, possibly suffixed | |
552 | with a random identifier in case <option>--ephemeral</option> | |
553 | mode is selected. If the root directory selected is the host's | |
554 | root directory the host's hostname is used as default | |
555 | instead.</para></listitem> | |
556 | </varlistentry> | |
557 | ||
b012e921 MB |
558 | <varlistentry> |
559 | <term><option>--hostname=</option></term> | |
560 | ||
561 | <listitem><para>Controls the hostname to set within the container, if different from the machine name. Expects | |
562 | a valid hostname as argument. If this option is used, the kernel hostname of the container will be set to this | |
563 | value, otherwise it will be initialized to the machine name as controlled by the <option>--machine=</option> | |
564 | option described above. The machine name is used for various aspect of identification of the container from the | |
565 | outside, the kernel hostname configurable with this option is useful for the container to identify itself from | |
566 | the inside. It is usually a good idea to keep both forms of identification synchronized, in order to avoid | |
567 | confusion. It is hence recommended to avoid usage of this option, and use <option>--machine=</option> | |
568 | exclusively. Note that regardless whether the container's hostname is initialized from the name set with | |
569 | <option>--hostname=</option> or the one set with <option>--machine=</option>, the container can later override | |
570 | its kernel hostname freely on its own as well.</para> | |
571 | </listitem> | |
572 | </varlistentry> | |
573 | ||
e735f4d4 MP |
574 | <varlistentry> |
575 | <term><option>--uuid=</option></term> | |
576 | ||
577 | <listitem><para>Set the specified UUID for the container. The | |
578 | init system will initialize | |
579 | <filename>/etc/machine-id</filename> from this if this file is | |
aa27b158 MP |
580 | not set yet. Note that this option takes effect only if |
581 | <filename>/etc/machine-id</filename> in the container is | |
582 | unpopulated.</para></listitem> | |
e735f4d4 | 583 | </varlistentry> |
bb4f798a MB |
584 | </variablelist> |
585 | ||
586 | </refsect2><refsect2> | |
587 | <title>Property Options</title> | |
e735f4d4 | 588 | |
bb4f798a | 589 | <variablelist> |
e735f4d4 | 590 | <varlistentry> |
1d42b86d | 591 | <term><option>-S</option></term> |
e735f4d4 MP |
592 | <term><option>--slice=</option></term> |
593 | ||
81c58355 MB |
594 | <listitem><para>Make the container part of the specified slice, instead of the default |
595 | <filename>machine.slice</filename>. This applies only if the machine is run in its own scope unit, i.e. if | |
596 | <option>--keep-unit</option> isn't used.</para> | |
e735f4d4 MP |
597 | </listitem> |
598 | </varlistentry> | |
599 | ||
e3bff60a MP |
600 | <varlistentry> |
601 | <term><option>--property=</option></term> | |
602 | ||
81c58355 MB |
603 | <listitem><para>Set a unit property on the scope unit to register for the machine. This applies only if the |
604 | machine is run in its own scope unit, i.e. if <option>--keep-unit</option> isn't used. Takes unit property | |
605 | assignments in the same format as <command>systemctl set-property</command>. This is useful to set memory | |
606 | limits and similar for container.</para> | |
e3bff60a MP |
607 | </listitem> |
608 | </varlistentry> | |
609 | ||
bb4f798a MB |
610 | <varlistentry> |
611 | <term><option>--register=</option></term> | |
612 | ||
613 | <listitem><para>Controls whether the container is registered with | |
614 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Takes a | |
615 | boolean argument, which defaults to <literal>yes</literal>. This option should be enabled when the container | |
616 | runs a full Operating System (more specifically: a system and service manager as PID 1), and is useful to | |
617 | ensure that the container is accessible via | |
618 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> and shown by | |
619 | tools such as <citerefentry | |
620 | project='man-pages'><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If the container | |
621 | does not run a service manager, it is recommended to set this option to | |
622 | <literal>no</literal>.</para></listitem> | |
623 | </varlistentry> | |
624 | ||
625 | <varlistentry> | |
626 | <term><option>--keep-unit</option></term> | |
627 | ||
628 | <listitem><para>Instead of creating a transient scope unit to run the container in, simply use the service or | |
629 | scope unit <command>systemd-nspawn</command> has been invoked in. If <option>--register=yes</option> is set | |
630 | this unit is registered with | |
631 | <citerefentry><refentrytitle>systemd-machined</refentrytitle><manvolnum>8</manvolnum></citerefentry>. This | |
632 | switch should be used if <command>systemd-nspawn</command> is invoked from within a service unit, and the | |
633 | service unit's sole purpose is to run a single <command>systemd-nspawn</command> container. This option is not | |
634 | available if run from a user session.</para> | |
635 | <para>Note that passing <option>--keep-unit</option> disables the effect of <option>--slice=</option> and | |
636 | <option>--property=</option>. Use <option>--keep-unit</option> and <option>--register=no</option> in | |
637 | combination to disable any kind of unit allocation or registration with | |
638 | <command>systemd-machined</command>.</para></listitem> | |
639 | </varlistentry> | |
640 | </variablelist> | |
641 | ||
642 | </refsect2><refsect2> | |
643 | <title>User Namespacing Options</title> | |
644 | ||
645 | <variablelist> | |
e3bff60a MP |
646 | <varlistentry> |
647 | <term><option>--private-users=</option></term> | |
648 | ||
aa27b158 MP |
649 | <listitem><para>Controls user namespacing. If enabled, the container will run with its own private set of UNIX |
650 | user and group ids (UIDs and GIDs). This involves mapping the private UIDs/GIDs used in the container (starting | |
651 | with the container's root user 0 and up) to a range of UIDs/GIDs on the host that are not used for other | |
652 | purposes (usually in the range beyond the host's UID/GID 65536). The parameter may be specified as follows:</para> | |
e3bff60a | 653 | |
aa27b158 | 654 | <orderedlist> |
8a584da2 MP |
655 | <listitem><para>If one or two colon-separated numbers are specified, user namespacing is turned on. The first |
656 | parameter specifies the first host UID/GID to assign to the container, the second parameter specifies the | |
657 | number of host UIDs/GIDs to assign to the container. If the second parameter is omitted, 65536 UIDs/GIDs are | |
658 | assigned.</para></listitem> | |
659 | ||
660 | <listitem><para>If the parameter is omitted, or true, user namespacing is turned on. The UID/GID range to | |
661 | use is determined automatically from the file ownership of the root directory of the container's directory | |
662 | tree. To use this option, make sure to prepare the directory tree in advance, and ensure that all files and | |
663 | directories in it are owned by UIDs/GIDs in the range you'd like to use. Also, make sure that used file ACLs | |
664 | exclusively reference UIDs/GIDs in the appropriate range. If this mode is used the number of UIDs/GIDs | |
665 | assigned to the container for use is 65536, and the UID/GID of the root directory must be a multiple of | |
666 | 65536.</para></listitem> | |
667 | ||
668 | <listitem><para>If the parameter is false, user namespacing is turned off. This is the default.</para> | |
669 | </listitem> | |
670 | ||
671 | <listitem><para>The special value <literal>pick</literal> turns on user namespacing. In this case the UID/GID | |
672 | range is automatically chosen. As first step, the file owner of the root directory of the container's | |
673 | directory tree is read, and it is checked that it is currently not used by the system otherwise (in | |
674 | particular, that no other container is using it). If this check is successful, the UID/GID range determined | |
675 | this way is used, similar to the behavior if "yes" is specified. If the check is not successful (and thus | |
676 | the UID/GID range indicated in the root directory's file owner is already used elsewhere) a new – currently | |
677 | unused – UID/GID range of 65536 UIDs/GIDs is randomly chosen between the host UID/GIDs of 524288 and | |
678 | 1878982656, always starting at a multiple of 65536. This setting implies | |
679 | <option>--private-users-chown</option> (see below), which has the effect that the files and directories in | |
680 | the container's directory tree will be owned by the appropriate users of the range picked. Using this option | |
681 | makes user namespace behavior fully automatic. Note that the first invocation of a previously unused | |
682 | container image might result in picking a new UID/GID range for it, and thus in the (possibly expensive) file | |
683 | ownership adjustment operation. However, subsequent invocations of the container will be cheap (unless of | |
684 | course the picked UID/GID range is assigned to a different use by then).</para></listitem> | |
aa27b158 MP |
685 | </orderedlist> |
686 | ||
687 | <para>It is recommended to assign at least 65536 UIDs/GIDs to each container, so that the usable UID/GID range in the | |
688 | container covers 16 bit. For best security, do not assign overlapping UID/GID ranges to multiple containers. It is | |
689 | hence a good idea to use the upper 16 bit of the host 32-bit UIDs/GIDs as container identifier, while the lower 16 | |
8a584da2 | 690 | bit encode the container UID/GID used. This is in fact the behavior enforced by the |
aa27b158 MP |
691 | <option>--private-users=pick</option> option.</para> |
692 | ||
693 | <para>When user namespaces are used, the GID range assigned to each container is always chosen identical to the | |
694 | UID range.</para> | |
695 | ||
696 | <para>In most cases, using <option>--private-users=pick</option> is the recommended option as it enhances | |
697 | container security massively and operates fully automatically in most cases.</para> | |
698 | ||
699 | <para>Note that the picked UID/GID range is not written to <filename>/etc/passwd</filename> or | |
700 | <filename>/etc/group</filename>. In fact, the allocation of the range is not stored persistently anywhere, | |
2897b343 MP |
701 | except in the file ownership of the files and directories of the container.</para> |
702 | ||
703 | <para>Note that when user namespacing is used file ownership on disk reflects this, and all of the container's | |
704 | files and directories are owned by the container's effective user and group IDs. This means that copying files | |
705 | from and to the container image requires correction of the numeric UID/GID values, according to the UID/GID | |
706 | shift applied.</para></listitem> | |
aa27b158 MP |
707 | </varlistentry> |
708 | ||
aa27b158 MP |
709 | <varlistentry> |
710 | <term><option>--private-users-chown</option></term> | |
711 | ||
712 | <listitem><para>If specified, all files and directories in the container's directory tree will adjusted so that | |
713 | they are owned to the appropriate UIDs/GIDs selected for the container (see above). This operation is | |
714 | potentially expensive, as it involves descending and iterating through the full directory tree of the | |
715 | container. Besides actual file ownership, file ACLs are adjusted as well.</para> | |
716 | ||
717 | <para>This option is implied if <option>--private-users=pick</option> is used. This option has no effect if | |
718 | user namespacing is not used.</para></listitem> | |
719 | </varlistentry> | |
e3bff60a | 720 | |
8a584da2 MP |
721 | <varlistentry> |
722 | <term><option>-U</option></term> | |
723 | ||
724 | <listitem><para>If the kernel supports the user namespaces feature, equivalent to | |
725 | <option>--private-users=pick --private-users-chown</option>, otherwise equivalent to | |
726 | <option>--private-users=no</option>.</para> | |
727 | ||
728 | <para>Note that <option>-U</option> is the default if the | |
729 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
730 | ||
731 | <para>Note: it is possible to undo the effect of <option>--private-users-chown</option> (or | |
732 | <option>-U</option>) on the file system by redoing the operation with the first UID of 0:</para> | |
733 | ||
734 | <programlisting>systemd-nspawn … --private-users=0 --private-users-chown</programlisting> | |
735 | </listitem> | |
736 | </varlistentry> | |
737 | ||
bb4f798a MB |
738 | </variablelist> |
739 | ||
740 | </refsect2><refsect2> | |
741 | <title>Networking Options</title> | |
742 | ||
743 | <variablelist> | |
744 | ||
e735f4d4 MP |
745 | <varlistentry> |
746 | <term><option>--private-network</option></term> | |
747 | ||
748 | <listitem><para>Disconnect networking of the container from | |
749 | the host. This makes all network interfaces unavailable in the | |
750 | container, with the exception of the loopback device and those | |
751 | specified with <option>--network-interface=</option> and | |
752 | configured with <option>--network-veth</option>. If this | |
753 | option is specified, the CAP_NET_ADMIN capability will be | |
754 | added to the set of capabilities the container retains. The | |
b012e921 MB |
755 | latter may be disabled by using <option>--drop-capability=</option>. |
756 | If this option is not specified (or implied by one of the options | |
757 | listed below), the container will have full access to the host network. | |
758 | </para></listitem> | |
e735f4d4 MP |
759 | </varlistentry> |
760 | ||
761 | <varlistentry> | |
762 | <term><option>--network-interface=</option></term> | |
763 | ||
764 | <listitem><para>Assign the specified network interface to the | |
765 | container. This will remove the specified interface from the | |
766 | calling namespace and place it in the container. When the | |
767 | container terminates, it is moved back to the host namespace. | |
768 | Note that <option>--network-interface=</option> implies | |
769 | <option>--private-network</option>. This option may be used | |
770 | more than once to add multiple network interfaces to the | |
771 | container.</para></listitem> | |
772 | </varlistentry> | |
773 | ||
774 | <varlistentry> | |
775 | <term><option>--network-macvlan=</option></term> | |
776 | ||
777 | <listitem><para>Create a <literal>macvlan</literal> interface | |
778 | of the specified Ethernet network interface and add it to the | |
779 | container. A <literal>macvlan</literal> interface is a virtual | |
780 | interface that adds a second MAC address to an existing | |
781 | physical Ethernet link. The interface in the container will be | |
782 | named after the interface on the host, prefixed with | |
783 | <literal>mv-</literal>. Note that | |
784 | <option>--network-macvlan=</option> implies | |
785 | <option>--private-network</option>. This option may be used | |
786 | more than once to add multiple network interfaces to the | |
787 | container.</para></listitem> | |
788 | </varlistentry> | |
789 | ||
790 | <varlistentry> | |
791 | <term><option>--network-ipvlan=</option></term> | |
792 | ||
793 | <listitem><para>Create an <literal>ipvlan</literal> interface | |
794 | of the specified Ethernet network interface and add it to the | |
795 | container. An <literal>ipvlan</literal> interface is a virtual | |
796 | interface, similar to a <literal>macvlan</literal> interface, | |
797 | which uses the same MAC address as the underlying interface. | |
798 | The interface in the container will be named after the | |
799 | interface on the host, prefixed with <literal>iv-</literal>. | |
800 | Note that <option>--network-ipvlan=</option> implies | |
801 | <option>--private-network</option>. This option may be used | |
802 | more than once to add multiple network interfaces to the | |
803 | container.</para></listitem> | |
804 | </varlistentry> | |
805 | ||
806 | <varlistentry> | |
807 | <term><option>-n</option></term> | |
808 | <term><option>--network-veth</option></term> | |
809 | ||
aa27b158 MP |
810 | <listitem><para>Create a virtual Ethernet link (<literal>veth</literal>) between host and container. The host |
811 | side of the Ethernet link will be available as a network interface named after the container's name (as | |
812 | specified with <option>--machine=</option>), prefixed with <literal>ve-</literal>. The container side of the | |
813 | Ethernet link will be named <literal>host0</literal>. The <option>--network-veth</option> option implies | |
814 | <option>--private-network</option>.</para> | |
815 | ||
816 | <para>Note that | |
817 | <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> | |
818 | includes by default a network file <filename>/usr/lib/systemd/network/80-container-ve.network</filename> | |
819 | matching the host-side interfaces created this way, which contains settings to enable automatic address | |
820 | provisioning on the created virtual link via DHCP, as well as automatic IP routing onto the host's external | |
821 | network interfaces. It also contains <filename>/usr/lib/systemd/network/80-container-host0.network</filename> | |
822 | matching the container-side interface created this way, containing settings to enable client side address | |
823 | assignment via DHCP. In case <filename>systemd-networkd</filename> is running on both the host and inside the | |
824 | container, automatic IP communication from the container to the host is thus available, with further | |
825 | connectivity to the external network.</para> | |
5a920b42 MP |
826 | |
827 | <para>Note that <option>--network-veth</option> is the default if the | |
828 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para> | |
bb4f798a MB |
829 | |
830 | <para>Note that on Linux network interface names may have a length of 15 characters at maximum, while | |
831 | container names may have a length up to 64 characters. As this option derives the host-side interface | |
832 | name from the container name the name is possibly truncated. Thus, care needs to be taken to ensure | |
833 | that interface names remain unique in this case, or even better container names are generally not | |
834 | chosen longer than 12 characters, to avoid the truncation. Alternatively, the | |
835 | <option>--network-veth-extra=</option> option may be used, which allows free configuration of the | |
836 | host-side interface name independently of the container name — but might require a bit more | |
837 | additional configuration in case bridging in a fashion similar to <option>--network-bridge=</option> | |
838 | is desired.</para> | |
aa27b158 | 839 | </listitem> |
e735f4d4 MP |
840 | </varlistentry> |
841 | ||
db2df898 MP |
842 | <varlistentry> |
843 | <term><option>--network-veth-extra=</option></term> | |
844 | ||
845 | <listitem><para>Adds an additional virtual Ethernet link | |
846 | between host and container. Takes a colon-separated pair of | |
847 | host interface name and container interface name. The latter | |
848 | may be omitted in which case the container and host sides will | |
849 | be assigned the same name. This switch is independent of | |
aa27b158 | 850 | <option>--network-veth</option>, and — in contrast — may be |
db2df898 MP |
851 | used multiple times, and allows configuration of the network |
852 | interface names. Note that <option>--network-bridge=</option> | |
853 | has no effect on interfaces created with | |
854 | <option>--network-veth-extra=</option>.</para></listitem> | |
855 | </varlistentry> | |
856 | ||
e735f4d4 MP |
857 | <varlistentry> |
858 | <term><option>--network-bridge=</option></term> | |
859 | ||
bb4f798a MB |
860 | <listitem><para>Adds the host side of the Ethernet link created with <option>--network-veth</option> |
861 | to the specified Ethernet bridge interface. Expects a valid network interface name of a bridge device | |
862 | as argument. Note that <option>--network-bridge=</option> implies <option>--network-veth</option>. If | |
863 | this option is used, the host side of the Ethernet link will use the <literal>vb-</literal> prefix | |
864 | instead of <literal>ve-</literal>. Regardless of the used naming prefix the same network interface | |
865 | name length limits imposed by Linux apply, along with the complications this creates (for details see | |
866 | above).</para></listitem> | |
e735f4d4 MP |
867 | </varlistentry> |
868 | ||
aa27b158 MP |
869 | <varlistentry> |
870 | <term><option>--network-zone=</option></term> | |
871 | ||
872 | <listitem><para>Creates a virtual Ethernet link (<literal>veth</literal>) to the container and adds it to an | |
873 | automatically managed Ethernet bridge interface. The bridge interface is named after the passed argument, | |
874 | prefixed with <literal>vz-</literal>. The bridge interface is automatically created when the first container | |
875 | configured for its name is started, and is automatically removed when the last container configured for its | |
876 | name exits. Hence, each bridge interface configured this way exists only as long as there's at least one | |
877 | container referencing it running. This option is very similar to <option>--network-bridge=</option>, besides | |
878 | this automatic creation/removal of the bridge device.</para> | |
879 | ||
880 | <para>This setting makes it easy to place multiple related containers on a common, virtual Ethernet-based | |
881 | broadcast domain, here called a "zone". Each container may only be part of one zone, but each zone may contain | |
882 | any number of containers. Each zone is referenced by its name. Names may be chosen freely (as long as they form | |
883 | valid network interface names when prefixed with <literal>vz-</literal>), and it is sufficient to pass the same | |
81c58355 | 884 | name to the <option>--network-zone=</option> switch of the various concurrently running containers to join |
aa27b158 MP |
885 | them in one zone.</para> |
886 | ||
887 | <para>Note that | |
888 | <citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> | |
889 | includes by default a network file <filename>/usr/lib/systemd/network/80-container-vz.network</filename> | |
890 | matching the bridge interfaces created this way, which contains settings to enable automatic address | |
891 | provisioning on the created virtual network via DHCP, as well as automatic IP routing onto the host's external | |
892 | network interfaces. Using <option>--network-zone=</option> is hence in most cases fully automatic and | |
893 | sufficient to connect multiple local containers in a joined broadcast domain to the host, with further | |
894 | connectivity to the external network.</para> | |
895 | </listitem> | |
896 | </varlistentry> | |
897 | ||
bb4f798a MB |
898 | <varlistentry> |
899 | <term><option>--network-namespace-path=</option></term> | |
900 | ||
901 | <listitem><para>Takes the path to a file representing a kernel | |
902 | network namespace that the container shall run in. The specified path | |
903 | should refer to a (possibly bind-mounted) network namespace file, as | |
904 | exposed by the kernel below <filename>/proc/$PID/ns/net</filename>. | |
905 | This makes the container enter the given network namespace. One of the | |
906 | typical use cases is to give a network namespace under | |
907 | <filename>/run/netns</filename> created by <citerefentry | |
908 | project='man-pages'><refentrytitle>ip-netns</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
909 | for example, <option>--network-namespace-path=/run/netns/foo</option>. | |
910 | Note that this option cannot be used together with other | |
911 | network-related options, such as <option>--private-network</option> | |
912 | or <option>--network-interface=</option>.</para></listitem> | |
913 | </varlistentry> | |
914 | ||
e735f4d4 MP |
915 | <varlistentry> |
916 | <term><option>-p</option></term> | |
917 | <term><option>--port=</option></term> | |
918 | ||
919 | <listitem><para>If private networking is enabled, maps an IP | |
920 | port on the host onto an IP port on the container. Takes a | |
921 | protocol specifier (either <literal>tcp</literal> or | |
922 | <literal>udp</literal>), separated by a colon from a host port | |
923 | number in the range 1 to 65535, separated by a colon from a | |
924 | container port number in the range from 1 to 65535. The | |
925 | protocol specifier and its separating colon may be omitted, in | |
926 | which case <literal>tcp</literal> is assumed. The container | |
86f210e9 | 927 | port number and its colon may be omitted, in which case the |
e735f4d4 | 928 | same port as the host port is implied. This option is only |
db2df898 | 929 | supported if private networking is used, such as with |
aa27b158 | 930 | <option>--network-veth</option>, <option>--network-zone=</option> |
e735f4d4 MP |
931 | <option>--network-bridge=</option>.</para></listitem> |
932 | </varlistentry> | |
bb4f798a | 933 | </variablelist> |
e735f4d4 | 934 | |
bb4f798a MB |
935 | </refsect2><refsect2> |
936 | <title>Security Options</title> | |
e735f4d4 | 937 | |
bb4f798a | 938 | <variablelist> |
e735f4d4 MP |
939 | <varlistentry> |
940 | <term><option>--capability=</option></term> | |
941 | ||
1d42b86d MB |
942 | <listitem><para>List one or more additional capabilities to grant the container. |
943 | Takes a comma-separated list of capability names, see | |
e735f4d4 | 944 | <citerefentry project='man-pages'><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry> |
1d42b86d MB |
945 | for more information. Note that the following capabilities will be granted in any way: |
946 | CAP_AUDIT_CONTROL, CAP_AUDIT_WRITE, CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_DAC_READ_SEARCH, | |
947 | CAP_FOWNER, CAP_FSETID, CAP_IPC_OWNER, CAP_KILL, CAP_LEASE, CAP_LINUX_IMMUTABLE, | |
948 | CAP_MKNOD, CAP_NET_BIND_SERVICE, CAP_NET_BROADCAST, CAP_NET_RAW, CAP_SETFCAP, | |
949 | CAP_SETGID, CAP_SETPCAP, CAP_SETUID, CAP_SYS_ADMIN, CAP_SYS_BOOT, CAP_SYS_CHROOT, | |
950 | CAP_SYS_NICE, CAP_SYS_PTRACE, CAP_SYS_RESOURCE, CAP_SYS_TTY_CONFIG. Also CAP_NET_ADMIN | |
951 | is retained if <option>--private-network</option> is specified. If the special value | |
952 | <literal>all</literal> is passed, all capabilities are retained.</para></listitem> | |
e735f4d4 MP |
953 | </varlistentry> |
954 | ||
955 | <varlistentry> | |
956 | <term><option>--drop-capability=</option></term> | |
957 | ||
958 | <listitem><para>Specify one or more additional capabilities to | |
959 | drop for the container. This allows running the container with | |
960 | fewer capabilities than the default (see | |
961 | above).</para></listitem> | |
962 | </varlistentry> | |
963 | ||
b012e921 MB |
964 | <varlistentry> |
965 | <term><option>--no-new-privileges=</option></term> | |
966 | ||
967 | <listitem><para>Takes a boolean argument. Specifies the value of the <constant>PR_SET_NO_NEW_PRIVS</constant> | |
968 | flag for the container payload. Defaults to off. When turned on the payload code of the container cannot | |
969 | acquire new privileges, i.e. the "setuid" file bit as well as file system capabilities will not have an effect | |
970 | anymore. See <citerefentry | |
971 | project='man-pages'><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry> for details | |
972 | about this flag. </para></listitem> | |
973 | </varlistentry> | |
974 | ||
f5e65279 MB |
975 | <varlistentry> |
976 | <term><option>--system-call-filter=</option></term> | |
977 | ||
978 | <listitem><para>Alter the system call filter applied to containers. Takes a space-separated list of system call | |
979 | names or group names (the latter prefixed with <literal>@</literal>, as listed by the | |
b012e921 MB |
980 | <command>syscall-filter</command> command of |
981 | <citerefentry><refentrytitle>systemd-analyze</refentrytitle><manvolnum>1</manvolnum></citerefentry>). Passed | |
f5e65279 MB |
982 | system calls will be permitted. The list may optionally be prefixed by <literal>~</literal>, in which case all |
983 | listed system calls are prohibited. If this command line option is used multiple times the configured lists are | |
984 | combined. If both a positive and a negative list (that is one system call list without and one with the | |
985 | <literal>~</literal> prefix) are configured, the negative list takes precedence over the positive list. Note | |
986 | that <command>systemd-nspawn</command> always implements a system call whitelist (as opposed to a blacklist), | |
987 | and this command line option hence adds or removes entries from the default whitelist, depending on the | |
988 | <literal>~</literal> prefix. Note that the applied system call filter is also altered implicitly if additional | |
989 | capabilities are passed using the <command>--capabilities=</command>.</para></listitem> | |
990 | </varlistentry> | |
991 | ||
bb4f798a MB |
992 | <varlistentry> |
993 | <term><option>-Z</option></term> | |
994 | <term><option>--selinux-context=</option></term> | |
995 | ||
996 | <listitem><para>Sets the SELinux security context to be used | |
997 | to label processes in the container.</para> | |
998 | </listitem> | |
999 | </varlistentry> | |
1000 | ||
1001 | <varlistentry> | |
1002 | <term><option>-L</option></term> | |
1003 | <term><option>--selinux-apifs-context=</option></term> | |
1004 | ||
1005 | <listitem><para>Sets the SELinux security context to be used | |
1006 | to label files in the virtual API file systems in the | |
1007 | container.</para> | |
1008 | </listitem> | |
1009 | </varlistentry> | |
1010 | </variablelist> | |
1011 | ||
1012 | </refsect2><refsect2> | |
1013 | <title>Resource Options</title> | |
1014 | ||
1015 | <variablelist> | |
1016 | ||
b012e921 MB |
1017 | <varlistentry> |
1018 | <term><option>--rlimit=</option></term> | |
1019 | ||
1020 | <listitem><para>Sets the specified POSIX resource limit for the container payload. Expects an assignment of the | |
1021 | form | |
1022 | <literal><replaceable>LIMIT</replaceable>=<replaceable>SOFT</replaceable>:<replaceable>HARD</replaceable></literal> | |
1023 | or <literal><replaceable>LIMIT</replaceable>=<replaceable>VALUE</replaceable></literal>, where | |
1024 | <replaceable>LIMIT</replaceable> should refer to a resource limit type, such as | |
1025 | <constant>RLIMIT_NOFILE</constant> or <constant>RLIMIT_NICE</constant>. The <replaceable>SOFT</replaceable> and | |
1026 | <replaceable>HARD</replaceable> fields should refer to the numeric soft and hard resource limit values. If the | |
1027 | second form is used, <replaceable>VALUE</replaceable> may specify a value that is used both as soft and hard | |
1028 | limit. In place of a numeric value the special string <literal>infinity</literal> may be used to turn off | |
1029 | resource limiting for the specific type of resource. This command line option may be used multiple times to | |
1030 | control limits on multiple limit types. If used multiple times for the same limit type, the last use | |
1031 | wins. For details about resource limits see <citerefentry | |
1032 | project='man-pages'><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry>. By default | |
1033 | resource limits for the container's init process (PID 1) are set to the same values the Linux kernel originally | |
1034 | passed to the host init system. Note that some resource limits are enforced on resources counted per user, in | |
1035 | particular <constant>RLIMIT_NPROC</constant>. This means that unless user namespacing is deployed | |
1036 | (i.e. <option>--private-users=</option> is used, see above), any limits set will be applied to the resource | |
1037 | usage of the same user on all local containers as well as the host. This means particular care needs to be | |
1038 | taken with these limits as they might be triggered by possibly less trusted code. Example: | |
1039 | <literal>--rlimit=RLIMIT_NOFILE=8192:16384</literal>.</para></listitem> | |
1040 | </varlistentry> | |
1041 | ||
1042 | <varlistentry> | |
1043 | <term><option>--oom-score-adjust=</option></term> | |
1044 | ||
1045 | <listitem><para>Changes the OOM ("Out Of Memory") score adjustment value for the container payload. This controls | |
1046 | <filename>/proc/self/oom_score_adj</filename> which influences the preference with which this container is | |
1047 | terminated when memory becomes scarce. For details see <citerefentry | |
1048 | project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Takes an | |
1049 | integer in the range -1000…1000.</para></listitem> | |
1050 | </varlistentry> | |
1051 | ||
1052 | <varlistentry> | |
1053 | <term><option>--cpu-affinity=</option></term> | |
1054 | ||
1055 | <listitem><para>Controls the CPU affinity of the container payload. Takes a comma separated list of CPU numbers | |
1056 | or number ranges (the latter's start and end value separated by dashes). See <citerefentry | |
1057 | project='man-pages'><refentrytitle>sched_setaffinity</refentrytitle><manvolnum>2</manvolnum></citerefentry> for | |
1058 | details.</para></listitem> | |
1059 | </varlistentry> | |
1060 | ||
e3bff60a | 1061 | <varlistentry> |
bb4f798a | 1062 | <term><option>--personality=</option></term> |
5a920b42 | 1063 | |
bb4f798a MB |
1064 | <listitem><para>Control the architecture ("personality") |
1065 | reported by | |
1066 | <citerefentry project='man-pages'><refentrytitle>uname</refentrytitle><manvolnum>2</manvolnum></citerefentry> | |
1067 | in the container. Currently, only <literal>x86</literal> and | |
1068 | <literal>x86-64</literal> are supported. This is useful when | |
1069 | running a 32-bit container on a 64-bit host. If this setting | |
1070 | is not used, the personality reported in the container is the | |
1071 | same as the one reported on the host.</para></listitem> | |
e735f4d4 | 1072 | </varlistentry> |
bb4f798a | 1073 | </variablelist> |
e735f4d4 | 1074 | |
bb4f798a MB |
1075 | </refsect2><refsect2> |
1076 | <title>Integration Options</title> | |
e735f4d4 | 1077 | |
bb4f798a | 1078 | <variablelist> |
b012e921 MB |
1079 | <varlistentry> |
1080 | <term><option>--resolv-conf=</option></term> | |
1081 | ||
1082 | <listitem><para>Configures how <filename>/etc/resolv.conf</filename> inside of the container (i.e. DNS | |
1083 | configuration synchronization from host to container) shall be handled. Takes one of <literal>off</literal>, | |
1084 | <literal>copy-host</literal>, <literal>copy-static</literal>, <literal>bind-host</literal>, | |
1085 | <literal>bind-static</literal>, <literal>delete</literal> or <literal>auto</literal>. If set to | |
1086 | <literal>off</literal> the <filename>/etc/resolv.conf</filename> file in the container is left as it is | |
1087 | included in the image, and neither modified nor bind mounted over. If set to <literal>copy-host</literal>, the | |
1088 | <filename>/etc/resolv.conf</filename> file from the host is copied into the container. Similar, if | |
1089 | <literal>bind-host</literal> is used, the file is bind mounted from the host into the container. If set to | |
1090 | <literal>copy-static</literal> the static <filename>resolv.conf</filename> file supplied with | |
1091 | <citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> is | |
1092 | copied into the container, and correspondingly <literal>bind-static</literal> bind mounts it there. If set to | |
1093 | <literal>delete</literal> the <filename>/etc/resolv.conf</filename> file in the container is deleted if it | |
1094 | exists. Finally, if set to <literal>auto</literal> the file is left as it is if private networking is turned on | |
1095 | (see <option>--private-network</option>). Otherwise, if <filename>systemd-resolved.service</filename> is | |
1096 | connectible its static <filename>resolv.conf</filename> file is used, and if not the host's | |
1097 | <filename>/etc/resolv.conf</filename> file is used. In the latter cases the file is copied if the image is | |
1098 | writable, and bind mounted otherwise. It's recommended to use <literal>copy</literal> if the container shall be | |
1099 | able to make changes to the DNS configuration on its own, deviating from the host's settings. Otherwise | |
1100 | <literal>bind</literal> is preferable, as it means direct changes to <filename>/etc/resolv.conf</filename> in | |
1101 | the container are not allowed, as it is a read-only bind mount (but note that if the container has enough | |
1102 | privileges, it might simply go ahead and unmount the bind mount anyway). Note that both if the file is bind | |
1103 | mounted and if it is copied no further propagation of configuration is generally done after the one-time early | |
1104 | initialization (this is because the file is usually updated through copying and renaming). Defaults to | |
1105 | <literal>auto</literal>.</para></listitem> | |
1106 | </varlistentry> | |
1107 | ||
1108 | <varlistentry> | |
1109 | <term><option>--timezone=</option></term> | |
1110 | ||
1111 | <listitem><para>Configures how <filename>/etc/localtime</filename> inside of the container (i.e. local timezone | |
1112 | synchronization from host to container) shall be handled. Takes one of <literal>off</literal>, | |
1113 | <literal>copy</literal>, <literal>bind</literal>, <literal>symlink</literal>, <literal>delete</literal> or | |
1114 | <literal>auto</literal>. If set to <literal>off</literal> the <filename>/etc/localtime</filename> file in the | |
1115 | container is left as it is included in the image, and neither modified nor bind mounted over. If set to | |
1116 | <literal>copy</literal> the <filename>/etc/localtime</filename> file of the host is copied into the | |
1117 | container. Similar, if <literal>bind</literal> is used, it is bind mounted from the host into the container. If | |
1118 | set to <literal>symlink</literal> a symlink from <filename>/etc/localtime</filename> in the container is | |
1119 | created pointing to the matching the timezone file of the container that matches the timezone setting on the | |
1120 | host. If set to <literal>delete</literal> the file in the container is deleted, should it exist. If set to | |
1121 | <literal>auto</literal> and the <filename>/etc/localtime</filename> file of the host is a symlink, then | |
1122 | <literal>symlink</literal> mode is used, and <literal>copy</literal> otherwise, except if the image is | |
1123 | read-only in which case <literal>bind</literal> is used instead. Defaults to | |
1124 | <literal>auto</literal>.</para></listitem> | |
1125 | </varlistentry> | |
1126 | ||
e735f4d4 | 1127 | <varlistentry> |
bb4f798a | 1128 | <term><option>--link-journal=</option></term> |
e735f4d4 | 1129 | |
bb4f798a MB |
1130 | <listitem><para>Control whether the container's journal shall |
1131 | be made visible to the host system. If enabled, allows viewing | |
1132 | the container's journal files from the host (but not vice | |
1133 | versa). Takes one of <literal>no</literal>, | |
1134 | <literal>host</literal>, <literal>try-host</literal>, | |
1135 | <literal>guest</literal>, <literal>try-guest</literal>, | |
1136 | <literal>auto</literal>. If <literal>no</literal>, the journal | |
1137 | is not linked. If <literal>host</literal>, the journal files | |
1138 | are stored on the host file system (beneath | |
1139 | <filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>) | |
1140 | and the subdirectory is bind-mounted into the container at the | |
1141 | same location. If <literal>guest</literal>, the journal files | |
1142 | are stored on the guest file system (beneath | |
1143 | <filename>/var/log/journal/<replaceable>machine-id</replaceable></filename>) | |
1144 | and the subdirectory is symlinked into the host at the same | |
1145 | location. <literal>try-host</literal> and | |
1146 | <literal>try-guest</literal> do the same but do not fail if | |
1147 | the host does not have persistent journaling enabled. If | |
1148 | <literal>auto</literal> (the default), and the right | |
1149 | subdirectory of <filename>/var/log/journal</filename> exists, | |
1150 | it will be bind mounted into the container. If the | |
1151 | subdirectory does not exist, no linking is performed. | |
1152 | Effectively, booting a container once with | |
1153 | <literal>guest</literal> or <literal>host</literal> will link | |
1154 | the journal persistently if further on the default of | |
1155 | <literal>auto</literal> is used.</para> | |
1156 | ||
1157 | <para>Note that <option>--link-journal=try-guest</option> is the default if the | |
1158 | <filename>systemd-nspawn@.service</filename> template unit file is used.</para></listitem> | |
e735f4d4 MP |
1159 | </varlistentry> |
1160 | ||
bb4f798a MB |
1161 | <varlistentry> |
1162 | <term><option>-j</option></term> | |
1163 | ||
1164 | <listitem><para>Equivalent to | |
1165 | <option>--link-journal=try-guest</option>.</para></listitem> | |
1166 | </varlistentry> | |
1167 | ||
1168 | </variablelist> | |
1169 | ||
1170 | </refsect2><refsect2> | |
1171 | <title>Mount Options</title> | |
1172 | ||
1173 | <variablelist> | |
1174 | ||
e735f4d4 MP |
1175 | <varlistentry> |
1176 | <term><option>--bind=</option></term> | |
1177 | <term><option>--bind-ro=</option></term> | |
1178 | ||
2897b343 MP |
1179 | <listitem><para>Bind mount a file or directory from the host into the container. Takes one of: a path |
1180 | argument — in which case the specified path will be mounted from the host to the same path in the container, or | |
1181 | a colon-separated pair of paths — in which case the first specified path is the source in the host, and the | |
1182 | second path is the destination in the container, or a colon-separated triple of source path, destination path | |
1183 | and mount options. The source path may optionally be prefixed with a <literal>+</literal> character. If so, the | |
1184 | source path is taken relative to the image's root directory. This permits setting up bind mounts within the | |
1185 | container image. The source path may be specified as empty string, in which case a temporary directory below | |
1186 | the host's <filename>/var/tmp</filename> directory is used. It is automatically removed when the container is | |
1187 | shut down. Mount options are comma-separated and currently, only <option>rbind</option> and | |
1188 | <option>norbind</option> are allowed, controlling whether to create a recursive or a regular bind | |
1189 | mount. Defaults to "rbind". Backslash escapes are interpreted, so <literal>\:</literal> may be used to embed | |
1190 | colons in either path. This option may be specified multiple times for creating multiple independent bind | |
52ad194e MB |
1191 | mount points. The <option>--bind-ro=</option> option creates read-only bind mounts.</para> |
1192 | ||
1193 | <para>Note that when this option is used in combination with <option>--private-users</option>, the resulting | |
1194 | mount points will be owned by the <constant>nobody</constant> user. That's because the mount and its files and | |
1195 | directories continue to be owned by the relevant host users and groups, which do not exist in the container, | |
1196 | and thus show up under the wildcard UID 65534 (nobody). If such bind mounts are created, it is recommended to | |
1197 | make them read-only, using <option>--bind-ro=</option>.</para></listitem> | |
e735f4d4 MP |
1198 | </varlistentry> |
1199 | ||
bb4f798a MB |
1200 | <varlistentry> |
1201 | <term><option>--inaccessible=</option></term> | |
1202 | ||
1203 | <listitem><para>Make the specified path inaccessible in the container. This over-mounts the specified path | |
1204 | (which must exist in the container) with a file node of the same type that is empty and has the most | |
1205 | restrictive access mode supported. This is an effective way to mask files, directories and other file system | |
1206 | objects from the container payload. This option may be used more than once in case all specified paths are | |
1207 | masked.</para></listitem> | |
1208 | </varlistentry> | |
1209 | ||
e735f4d4 MP |
1210 | <varlistentry> |
1211 | <term><option>--tmpfs=</option></term> | |
1212 | ||
bb4f798a MB |
1213 | <listitem><para>Mount a tmpfs file system into the container. Takes a single absolute path argument that |
1214 | specifies where to mount the tmpfs instance to (in which case the directory access mode will be chosen as 0755, | |
1215 | owned by root/root), or optionally a colon-separated pair of path and mount option string that is used for | |
1216 | mounting (in which case the kernel default for access mode and owner will be chosen, unless otherwise | |
1217 | specified). Backslash escapes are interpreted in the path, so <literal>\:</literal> may be used to embed colons | |
1218 | in the path.</para> | |
1219 | ||
1220 | <para>Note that this option cannot be used to replace the root file system of the container with a temporary | |
1221 | file system. However, the <option>--volatile=</option> option described below provides similar | |
1222 | functionality, with a focus on implementing stateless operating system images.</para></listitem> | |
e735f4d4 MP |
1223 | </varlistentry> |
1224 | ||
e3bff60a MP |
1225 | <varlistentry> |
1226 | <term><option>--overlay=</option></term> | |
1227 | <term><option>--overlay-ro=</option></term> | |
1228 | ||
1229 | <listitem><para>Combine multiple directory trees into one | |
1230 | overlay file system and mount it into the container. Takes a | |
1231 | list of colon-separated paths to the directory trees to | |
1232 | combine and the destination mount point.</para> | |
1233 | ||
13d276d0 MP |
1234 | <para>Backslash escapes are interpreted in the paths, so |
1235 | <literal>\:</literal> may be used to embed colons in the paths. | |
1236 | </para> | |
1237 | ||
e3bff60a MP |
1238 | <para>If three or more paths are specified, then the last |
1239 | specified path is the destination mount point in the | |
1240 | container, all paths specified before refer to directory trees | |
1241 | on the host and are combined in the specified order into one | |
1242 | overlay file system. The left-most path is hence the lowest | |
1243 | directory tree, the second-to-last path the highest directory | |
1244 | tree in the stacking order. If <option>--overlay-ro=</option> | |
db2df898 | 1245 | is used instead of <option>--overlay=</option>, a read-only |
e3bff60a | 1246 | overlay file system is created. If a writable overlay file |
db2df898 | 1247 | system is created, all changes made to it are written to the |
e3bff60a MP |
1248 | highest directory tree in the stacking order, i.e. the |
1249 | second-to-last specified.</para> | |
1250 | ||
1251 | <para>If only two paths are specified, then the second | |
1252 | specified path is used both as the top-level directory tree in | |
1253 | the stacking order as seen from the host, as well as the mount | |
1254 | point for the overlay file system in the container. At least | |
1255 | two paths have to be specified.</para> | |
1256 | ||
2897b343 MP |
1257 | <para>The source paths may optionally be prefixed with <literal>+</literal> character. If so they are taken |
1258 | relative to the image's root directory. The uppermost source path may also be specified as empty string, in | |
1259 | which case a temporary directory below the host's <filename>/var/tmp</filename> is used. The directory is | |
1260 | removed automatically when the container is shut down. This behaviour is useful in order to make read-only | |
1261 | container directories writable while the container is running. For example, use the | |
1262 | <literal>--overlay=+/var::/var</literal> option in order to automatically overlay a writable temporary | |
1263 | directory on a read-only <filename>/var</filename> directory.</para> | |
1264 | ||
e3bff60a MP |
1265 | <para>For details about overlay file systems, see <ulink |
1266 | url="https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt">overlayfs.txt</ulink>. Note | |
1267 | that the semantics of overlay file systems are substantially | |
1268 | different from normal file systems, in particular regarding | |
1269 | reported device and inode information. Device and inode | |
1270 | information may change for a file while it is being written | |
1271 | to, and processes might see out-of-date versions of files at | |
1272 | times. Note that this switch automatically derives the | |
1273 | <literal>workdir=</literal> mount option for the overlay file | |
1274 | system from the top-level directory tree, making it a sibling | |
1275 | of it. It is hence essential that the top-level directory tree | |
1276 | is not a mount point itself (since the working directory must | |
1277 | be on the same file system as the top-most directory | |
1278 | tree). Also note that the <literal>lowerdir=</literal> mount | |
1279 | option receives the paths to stack in the opposite order of | |
bb4f798a | 1280 | this switch.</para> |
e3bff60a | 1281 | |
bb4f798a MB |
1282 | <para>Note that this option cannot be used to replace the root file system of the container with an overlay |
1283 | file system. However, the <option>--volatile=</option> option described above provides similar functionality, | |
1284 | with a focus on implementing stateless operating system images.</para></listitem> | |
e735f4d4 | 1285 | </varlistentry> |
bb4f798a | 1286 | </variablelist> |
e735f4d4 | 1287 | |
bb4f798a MB |
1288 | </refsect2><refsect2> |
1289 | <title>Input/Output Options</title> | |
e735f4d4 | 1290 | |
bb4f798a | 1291 | <variablelist> |
d9dfd233 | 1292 | <varlistentry> |
bb4f798a MB |
1293 | <term><option>--console=</option><replaceable>MODE</replaceable></term> |
1294 | ||
1295 | <listitem><para>Configures how to set up standard input, output and error output for the container payload, as | |
1296 | well as the <filename>/dev/console</filename> device for the container. Takes one of | |
1297 | <option>interactive</option>, <option>read-only</option>, <option>passive</option> or <option>pipe</option>. If | |
1298 | <option>interactive</option> a pseudo-TTY is allocated and made available as <filename>/dev/console</filename> | |
1299 | in the container. It is then bi-directionally connected to the standard input and output passed to | |
1300 | <command>systemd-nspawn</command>. <option>read-only</option> is similar but only the output of the container | |
1301 | is propagated and no input from the caller is read. In <option>passive</option> mode a pseudo TTY is allocated, | |
1302 | but it is not connected anywhere. Finally, in <option>pipe</option> mode no pseudo TTY is allocated, but the | |
1303 | passed standard input, output and error output file descriptors are passed on — as they are — to the container | |
1304 | payload. In this mode <filename>/dev/console</filename> will not exist in the container. Note that in this mode | |
1305 | the container payload generally cannot be a full init system as init systems tend to require | |
1306 | <filename>/dev/console</filename> to be available. On the other hand, in this mode container invocations can be | |
1307 | used within shell pipelines. This is because intermediary pseudo TTYs do not permit independent bidirectional | |
1308 | propagation of the end-of-file (EOF) condition, which is necessary for shell pipelines to work | |
1309 | correctly.</para> | |
1310 | ||
1311 | <para>Note that the <option>pipe</option> mode should be used carefully, as passing arbitrary file descriptors | |
1312 | to less trusted container payloads might open up unwanted interfaces for access by the container payload. For | |
1313 | example, if a passed file descriptor refers to a TTY of some form, APIs such as <constant>TIOCSTI</constant> | |
1314 | may be used to synthesize input that might be used for escaping the container. Hence <option>pipe</option> mode | |
1315 | should only be used if the payload is sufficiently trusted or when the standard input/output/error output file | |
1316 | descriptors are known safe, for example pipes. Defaults to <option>interactive</option> if | |
1317 | <command>systemd-nspawn</command> is invoked from a terminal, and <option>read-only</option> | |
1318 | otherwise.</para></listitem> | |
d9dfd233 MP |
1319 | </varlistentry> |
1320 | ||
5a920b42 | 1321 | <varlistentry> |
bb4f798a MB |
1322 | <term><option>--pipe</option></term> |
1323 | <term><option>-P</option></term> | |
5a920b42 | 1324 | |
bb4f798a | 1325 | <listitem><para>Equivalent to <option>--console=pipe</option>.</para></listitem> |
5a920b42 MP |
1326 | </varlistentry> |
1327 | ||
bb4f798a | 1328 | <xi:include href="standard-options.xml" xpointer="no-pager" /> |
e735f4d4 MP |
1329 | <xi:include href="standard-options.xml" xpointer="help" /> |
1330 | <xi:include href="standard-options.xml" xpointer="version" /> | |
1331 | </variablelist> | |
bb4f798a | 1332 | </refsect2> |
e735f4d4 MP |
1333 | </refsect1> |
1334 | ||
bb4f798a MB |
1335 | <xi:include href="less-variables.xml" /> |
1336 | ||
e735f4d4 MP |
1337 | <refsect1> |
1338 | <title>Examples</title> | |
1339 | ||
1340 | <example> | |
52ad194e MB |
1341 | <title>Download a |
1342 | <ulink url="https://getfedora.org">Fedora</ulink> image and start a shell in it</title> | |
e735f4d4 | 1343 | |
2897b343 | 1344 | <programlisting># machinectl pull-raw --verify=no \ |
b012e921 MB |
1345 | https://download.fedoraproject.org/pub/fedora/linux/releases/&fedora_latest_version;/Cloud/x86_64/images/Fedora-Cloud-Base-&fedora_latest_version;-&fedora_cloud_release;.x86_64.raw.xz |
1346 | # systemd-nspawn -M Fedora-Cloud-Base-&fedora_latest_version;-&fedora_cloud_release;.x86_64.raw</programlisting> | |
e735f4d4 MP |
1347 | |
1348 | <para>This downloads an image using | |
1349 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
1350 | and opens a shell in it.</para> | |
1351 | </example> | |
1352 | ||
1353 | <example> | |
1354 | <title>Build and boot a minimal Fedora distribution in a container</title> | |
1355 | ||
b012e921 | 1356 | <programlisting># dnf -y --releasever=&fedora_latest_version; --installroot=/var/lib/machines/f&fedora_latest_version; \ |
2897b343 MP |
1357 | --disablerepo='*' --enablerepo=fedora --enablerepo=updates install \ |
1358 | systemd passwd dnf fedora-release vim-minimal | |
b012e921 | 1359 | # systemd-nspawn -bD /var/lib/machines/f&fedora_latest_version;</programlisting> |
663996b3 | 1360 | |
e735f4d4 | 1361 | <para>This installs a minimal Fedora distribution into the |
b012e921 | 1362 | directory <filename noindex='true'>/var/lib/machines/f&fedora_latest_version;</filename> |
52ad194e MB |
1363 | and then boots an OS in a namespace container in it. Because the installation |
1364 | is located underneath the standard <filename>/var/lib/machines/</filename> | |
1365 | directory, it is also possible to start the machine using | |
b012e921 | 1366 | <command>systemd-nspawn -M f&fedora_latest_version;</command>.</para> |
e735f4d4 | 1367 | </example> |
663996b3 | 1368 | |
e735f4d4 MP |
1369 | <example> |
1370 | <title>Spawn a shell in a container of a minimal Debian unstable distribution</title> | |
663996b3 | 1371 | |
1d42b86d | 1372 | <programlisting># debootstrap unstable ~/debian-tree/ |
663996b3 MS |
1373 | # systemd-nspawn -D ~/debian-tree/</programlisting> |
1374 | ||
e735f4d4 MP |
1375 | <para>This installs a minimal Debian unstable distribution into |
1376 | the directory <filename>~/debian-tree/</filename> and then | |
1377 | spawns a shell in a namespace container in it.</para> | |
52ad194e MB |
1378 | |
1379 | <para><command>debootstrap</command> supports | |
1380 | <ulink url="https://www.debian.org">Debian</ulink>, | |
1381 | <ulink url="https://www.ubuntu.com">Ubuntu</ulink>, | |
1382 | and <ulink url="https://www.tanglu.org">Tanglu</ulink> | |
1383 | out of the box, so the same command can be used to install any of those. For other | |
1384 | distributions from the Debian family, a mirror has to be specified, see | |
1385 | <citerefentry project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>. | |
1386 | </para> | |
e735f4d4 | 1387 | </example> |
663996b3 | 1388 | |
e735f4d4 | 1389 | <example> |
52ad194e MB |
1390 | <title>Boot a minimal |
1391 | <ulink url="https://www.archlinux.org">Arch Linux</ulink> distribution in a container</title> | |
663996b3 | 1392 | |
e735f4d4 | 1393 | <programlisting># pacstrap -c -d ~/arch-tree/ base |
663996b3 MS |
1394 | # systemd-nspawn -bD ~/arch-tree/</programlisting> |
1395 | ||
e3bff60a | 1396 | <para>This installs a minimal Arch Linux distribution into the |
e735f4d4 MP |
1397 | directory <filename>~/arch-tree/</filename> and then boots an OS |
1398 | in a namespace container in it.</para> | |
1399 | </example> | |
663996b3 | 1400 | |
81c58355 | 1401 | <example> |
52ad194e MB |
1402 | <title>Install the |
1403 | <ulink url="https://software.opensuse.org/distributions/tumbleweed">OpenSUSE Tumbleweed</ulink> | |
1404 | rolling distribution</title> | |
81c58355 MB |
1405 | |
1406 | <programlisting># zypper --root=/var/lib/machines/tumbleweed ar -c \ | |
1407 | https://download.opensuse.org/tumbleweed/repo/oss tumbleweed | |
1408 | # zypper --root=/var/lib/machines/tumbleweed refresh | |
1409 | # zypper --root=/var/lib/machines/tumbleweed install --no-recommends \ | |
1410 | systemd shadow zypper openSUSE-release vim | |
1411 | # systemd-nspawn -M tumbleweed passwd root | |
1412 | # systemd-nspawn -M tumbleweed -b</programlisting> | |
1413 | </example> | |
1414 | ||
e735f4d4 | 1415 | <example> |
2897b343 | 1416 | <title>Boot into an ephemeral snapshot of the host system</title> |
663996b3 | 1417 | |
e735f4d4 | 1418 | <programlisting># systemd-nspawn -D / -xb</programlisting> |
60f067b4 | 1419 | |
2897b343 MP |
1420 | <para>This runs a copy of the host system in a snapshot which is removed immediately when the container |
1421 | exits. All file system changes made during runtime will be lost on shutdown, hence.</para> | |
e735f4d4 | 1422 | </example> |
60f067b4 | 1423 | |
e735f4d4 MP |
1424 | <example> |
1425 | <title>Run a container with SELinux sandbox security contexts</title> | |
60f067b4 | 1426 | |
e735f4d4 | 1427 | <programlisting># chcon system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 -R /srv/container |
2897b343 MP |
1428 | # systemd-nspawn -L system_u:object_r:svirt_sandbox_file_t:s0:c0,c1 \ |
1429 | -Z system_u:system_r:svirt_lxc_net_t:s0:c0,c1 -D /srv/container /bin/sh</programlisting> | |
1430 | </example> | |
1431 | ||
1432 | <example> | |
1433 | <title>Run a container with an OSTree deployment</title> | |
1434 | ||
1435 | <programlisting># systemd-nspawn -b -i ~/image.raw \ | |
1436 | --pivot-root=/ostree/deploy/$OS/deploy/$CHECKSUM:/sysroot \ | |
1437 | --bind=+/sysroot/ostree/deploy/$OS/var:/var</programlisting> | |
e735f4d4 MP |
1438 | </example> |
1439 | </refsect1> | |
1440 | ||
1441 | <refsect1> | |
1442 | <title>Exit status</title> | |
1443 | ||
1444 | <para>The exit code of the program executed in the container is | |
1445 | returned.</para> | |
1446 | </refsect1> | |
1447 | ||
1448 | <refsect1> | |
1449 | <title>See Also</title> | |
1450 | <para> | |
1451 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
d9dfd233 | 1452 | <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
e735f4d4 MP |
1453 | <citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
1454 | <citerefentry project='mankier'><refentrytitle>dnf</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
e735f4d4 MP |
1455 | <citerefentry project='die-net'><refentrytitle>debootstrap</refentrytitle><manvolnum>8</manvolnum></citerefentry>, |
1456 | <citerefentry project='archlinux'><refentrytitle>pacman</refentrytitle><manvolnum>8</manvolnum></citerefentry>, | |
81c58355 | 1457 | <citerefentry project='mankier'><refentrytitle>zypper</refentrytitle><manvolnum>8</manvolnum></citerefentry>, |
e735f4d4 MP |
1458 | <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
1459 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
e3bff60a | 1460 | <citerefentry project='man-pages'><refentrytitle>btrfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> |
e735f4d4 MP |
1461 | </para> |
1462 | </refsect1> | |
663996b3 MS |
1463 | |
1464 | </refentry> |