system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-22 02:34:54 +00:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

nspawn: Rewrap --overlay docs

Browse source
This commit is contained in:
Daan De Meyer 2022-07-11 21:43:41 +02:00
parent a50947c56b
commit f075e32ca1
1 changed files with 16 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
man/systemd-nspawn.xml
View file

@ -1455,33 +1455,25 @@ After=sys-subsystem-net-devices-ens1.device</programlisting>
<term><option>--overlay=</option></term>
<term><option>--overlay-ro=</option></term>
<listitem><para>Combine multiple directory trees into one
overlay file system and mount it into the container. Takes a
list of colon-separated paths to the directory trees to
combine and the destination mount point.</para>
<listitem><para>Combine multiple directory trees into one overlay file system and mount it into the
container. Takes a list of colon-separated paths to the directory trees to combine and the
destination mount point.</para>
<para>Backslash escapes are interpreted in the paths, so
<literal>\:</literal> may be used to embed colons in the paths.
<para>Backslash escapes are interpreted in the paths, so <literal>\:</literal> may be used to embed
colons in the paths.</para>
<para>If three or more paths are specified, then the last specified path is the destination mount
point in the container, all paths specified before refer to directory trees on the host and are
combined in the specified order into one overlay file system. The left-most path is hence the lowest
directory tree, the second-to-last path the highest directory tree in the stacking order. If
<option>--overlay-ro=</option> is used instead of <option>--overlay=</option>, a read-only overlay
file system is created. If a writable overlay file system is created, all changes made to it are
written to the highest directory tree in the stacking order, i.e. the second-to-last specified.
</para>
<para>If three or more paths are specified, then the last
specified path is the destination mount point in the
container, all paths specified before refer to directory trees
on the host and are combined in the specified order into one
overlay file system. The left-most path is hence the lowest
directory tree, the second-to-last path the highest directory
tree in the stacking order. If <option>--overlay-ro=</option>
is used instead of <option>--overlay=</option>, a read-only
overlay file system is created. If a writable overlay file
system is created, all changes made to it are written to the
highest directory tree in the stacking order, i.e. the
second-to-last specified.</para>
<para>If only two paths are specified, then the second
specified path is used both as the top-level directory tree in
the stacking order as seen from the host, as well as the mount
point for the overlay file system in the container. At least
two paths have to be specified.</para>
<para>If only two paths are specified, then the second specified path is used both as the top-level
directory tree in the stacking order as seen from the host, as well as the mount point for the
overlay file system in the container. At least two paths have to be specified.</para>
<para>The source paths may optionally be prefixed with <literal>+</literal> character. If so they are
taken relative to the image's root directory. The uppermost source path may also be specified as an