picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: document that --volatile=yes is not supported for split /usr systems

Browse source
This commit is contained in:
Lennart Poettering 2019-07-29 09:45:11 +02:00
parent 07b9f3f03c
commit 2e542f4e62
1 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
man/systemd-nspawn.xml
View file

@ -368,12 +368,16 @@
<citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
details.</para> details.</para>
<para>Note that setting this option to <option>yes</option> or <option>state</option> will only work correctly <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work
with operating systems in the container that can boot up with only <filename>/usr</filename> mounted, and are correctly with operating systems in the container that can boot up with only
able to automatically populate <filename>/var</filename>, and also <filename>/etc</filename> in case of <filename>/usr/</filename> mounted, and are able to automatically populate <filename>/var/</filename>
<literal>--volatile=yes</literal>. The <option>overlay</option> option does not require any particular (and <filename>/etc/</filename> in case of <literal>--volatile=yes</literal>). Specifically, this
preparations in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file means that operating systems that follow the historic split of <filename>/bin/</filename> and
systems in a number of ways, and hence compatibility is limited.</para></listitem> <filename>/lib/</filename> (and related directories) from <filename>/usr/</filename> (i.e. where the
former are not symlinks into the latter) are not supported by <literal>--volatile=yes</literal> as
container payload. The <option>overlay</option> option does not require any particular preparations
in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file systems
in a number of ways, and hence compatibility is limited.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>