|
181 | 181 | <varlistentry> |
182 | 182 | <term><option>--template=</option></term> |
183 | 183 |
|
184 | | - <listitem><para>Directory or <literal>btrfs</literal> |
185 | | - subvolume to use as template for the container's root |
186 | | - directory. If this is specified and the container's root |
187 | | - directory (as configured by <option>--directory=</option>) |
188 | | - does not yet exist it is created as <literal>btrfs</literal> |
189 | | - subvolume and populated from this template tree. Ideally, the |
190 | | - specified template path refers to the root of a |
191 | | - <literal>btrfs</literal> subvolume, in which case a simple |
192 | | - copy-on-write snapshot is taken, and populating the root |
193 | | - directory is instant. If the specified template path does not |
194 | | - refer to the root of a <literal>btrfs</literal> subvolume (or |
195 | | - not even to a <literal>btrfs</literal> file system at all), |
196 | | - the tree is copied, which can be substantially more |
197 | | - time-consuming. Note that if this option is used the |
198 | | - container's root directory (in contrast to the template |
199 | | - directory!) must be located on a <literal>btrfs</literal> file |
200 | | - system, so that the <literal>btrfs</literal> subvolume may be |
201 | | - created. May not be specified together with |
202 | | - <option>--image=</option> or |
| 184 | + <listitem><para>Directory or <literal>btrfs</literal> subvolume to use as template for the container's root |
| 185 | + directory. If this is specified and the container's root directory (as configured by |
| 186 | + <option>--directory=</option>) does not yet exist it is created as <literal>btrfs</literal> snapshot (if |
| 187 | + supported) or plain directory (otherwise) and populated from this template tree. Ideally, the specified |
| 188 | + template path refers to the root of a <literal>btrfs</literal> subvolume, in which case a simple copy-on-write |
| 189 | + snapshot is taken, and populating the root directory is instant. If the specified template path does not refer |
| 190 | + to the root of a <literal>btrfs</literal> subvolume (or not even to a <literal>btrfs</literal> file system at |
| 191 | + all), the tree is copied (though possibly in a copy-on-write scheme — if the file system supports that), which |
| 192 | + can be substantially more time-consuming. May not be specified together with <option>--image=</option> or |
203 | 193 | <option>--ephemeral</option>.</para> |
204 | 194 |
|
205 | 195 | <para>Note that this switch leaves host name, machine ID and |
|
211 | 201 | <term><option>-x</option></term> |
212 | 202 | <term><option>--ephemeral</option></term> |
213 | 203 |
|
214 | | - <listitem><para>If specified, the container is run with a |
215 | | - temporary <literal>btrfs</literal> snapshot of its root |
216 | | - directory (as configured with <option>--directory=</option>), |
217 | | - that is removed immediately when the container terminates. |
218 | | - This option is only supported if the root file system is |
219 | | - <literal>btrfs</literal>. May not be specified together with |
220 | | - <option>--image=</option> or |
| 204 | + <listitem><para>If specified, the container is run with a temporary snapshot of its file system that is removed |
| 205 | + immediately when the container terminates. May not be specified together with |
221 | 206 | <option>--template=</option>.</para> |
222 | 207 | <para>Note that this switch leaves host name, machine ID and |
223 | 208 | all other settings that could identify the instance |
|
252 | 237 | Partitions Specification</ulink>.</para></listitem> |
253 | 238 | </itemizedlist> |
254 | 239 |
|
255 | | - <para>Any other partitions, such as foreign partitions, swap |
256 | | - partitions or EFI system partitions are not mounted. May not |
257 | | - be specified together with <option>--directory=</option>, |
258 | | - <option>--template=</option> or |
259 | | - <option>--ephemeral</option>.</para></listitem> |
| 240 | + <para>On GPT images, if an EFI System Partition (ESP) is discovered, it is automatically mounted to |
| 241 | + <filename>/efi</filename> (or <filename>/boot</filename> as fallback) in case a directory by this name exists |
| 242 | + and is empty.</para> |
| 243 | + |
| 244 | + <para>Any other partitions, such as foreign partitions or swap partitions are not mounted. May not be specified |
| 245 | + together with <option>--directory=</option>, <option>--template=</option>.</para></listitem> |
260 | 246 | </varlistentry> |
261 | 247 |
|
262 | 248 | <varlistentry> |
|
1056 | 1042 | </example> |
1057 | 1043 |
|
1058 | 1044 | <example> |
1059 | | - <title>Boot into an ephemeral <literal>btrfs</literal> snapshot of the host system</title> |
| 1045 | + <title>Boot into an ephemeral snapshot of the host system</title> |
1060 | 1046 |
|
1061 | 1047 | <programlisting># systemd-nspawn -D / -xb</programlisting> |
1062 | 1048 |
|
1063 | | - <para>This runs a copy of the host system in a |
1064 | | - <literal>btrfs</literal> snapshot which is removed immediately |
1065 | | - when the container exits. All file system changes made during |
1066 | | - runtime will be lost on shutdown, hence.</para> |
| 1049 | + <para>This runs a copy of the host system in a snapshot which is removed immediately when the container |
| 1050 | + exits. All file system changes made during runtime will be lost on shutdown, hence.</para> |
1067 | 1051 | </example> |
1068 | 1052 |
|
1069 | 1053 | <example> |
|
0 commit comments