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