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

man: document nspawn's new --volatile switch

Browse source
This commit is contained in:
Lennart Poettering 2014-07-04 12:17:12 +02:00
parent c38d2eb828
commit 108e8cd11e
1 changed files with 43 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
man/systemd-nspawn.xml
View file

@ -644,6 +644,49 @@
of the container OS itself.</para></listitem>
</varlistentry>
<varlistentry>
<term><option>--volatile</option><replaceable>=MODE</replaceable></term>
<listitem><para>Boots the container in
volatile (ephemeral) mode. When no
mode parameter is passed or when mode
is specified as <literal>yes</literal>
full volatile mode is enabled. This
means the root directory is mounted as
mostly unpopulated
<literal>tmpfs</literal> instance, and
<filename>/usr</filename> from the OS
tree is mounted into it, read-only
(the system thus starts up with
read-only OS resources, but pristine
state and configuration, any changes
to the either are lost on
shutdown). When the mode parameter is
specified as <literal>state</literal>
the OS tree is mounted read-only, but
<filename>/var</filename> is mounted
as <literal>tmpfs</literal> instance
into it (the system thus starts up
with read-only OS resources and
configuration, but prestine state, any
changes to the latter are lost on
shutdown). When the mode parameter is
specified as <literal>no</literal>
(the default) the whole OS tree is made
available writable.</para>
<para>Note that setting this to
<literal>yes</literal> or
<literal>state</literal> will only
work correctly with operating systems
in the container that can boot up with
only <filename>/usr</filename>
mounted, and are able to populate
<filename>/var</filename>
automatically, as
needed.</para></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="help" />
<xi:include href="standard-options.xml" xpointer="version" />
</variablelist>