diff options
| author | Lennart Poettering <lennart@poettering.net> | 2019-07-29 09:45:11 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2019-07-29 11:31:23 +0200 |
| commit | 2e542f4e62f770865bac6d6b2ad32d802a1523a7 (patch) | |
| tree | add77b9d798bfc10a7fa1f5907cff9e79f592628 | |
| parent | 07b9f3f03c8a105483231b8fa97d673c041c584c (diff) | |
| download | systemd-2e542f4e62f770865bac6d6b2ad32d802a1523a7.tar.gz | |
man: document that --volatile=yes is not supported for split /usr systems
| -rw-r--r-- | man/systemd-nspawn.xml | 16 |
1 files changed, 10 insertions, 6 deletions
diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 8c1a1e6871..9f0be96b26 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -368,12 +368,16 @@ <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for details.</para> - <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work correctly - with operating systems in the container that can boot up with only <filename>/usr</filename> mounted, and are - able to automatically populate <filename>/var</filename>, and also <filename>/etc</filename> in case of - <literal>--volatile=yes</literal>. 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> + <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work + correctly with operating systems in the container that can boot up with only + <filename>/usr/</filename> mounted, and are able to automatically populate <filename>/var/</filename> + (and <filename>/etc/</filename> in case of <literal>--volatile=yes</literal>). Specifically, this + means that operating systems that follow the historic split of <filename>/bin/</filename> and + <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> |