|
1 | | -<?xml version='1.0'?> <!--*-nxml-*--> |
| 1 | +<?xml version='1.0'?> <!--*- Mode: nxml; nxml-child-indent: 2; indent-tabs-mode: nil -*--> |
2 | 2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
3 | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> |
4 | 4 |
|
|
748 | 748 | </varlistentry> |
749 | 749 |
|
750 | 750 | <varlistentry> |
751 | | - <term><option>--volatile</option><replaceable>=MODE</replaceable></term> |
| 751 | + <term><option>--volatile</option></term> |
| 752 | + <term><option>--volatile=</option><replaceable>MODE</replaceable></term> |
752 | 753 |
|
753 | 754 | <listitem><para>Boots the container in volatile mode. When no |
754 | 755 | mode parameter is passed or when mode is specified as |
755 | | - <literal>yes</literal> full volatile mode is enabled. This |
| 756 | + <option>yes</option> full volatile mode is enabled. This |
756 | 757 | means the root directory is mounted as mostly unpopulated |
757 | 758 | <literal>tmpfs</literal> instance, and |
758 | 759 | <filename>/usr</filename> from the OS tree is mounted into it, |
759 | 760 | read-only (the system thus starts up with read-only OS |
760 | 761 | resources, but pristine state and configuration, any changes |
761 | 762 | to the either are lost on shutdown). When the mode parameter |
762 | | - is specified as <literal>state</literal> the OS tree is |
| 763 | + is specified as <option>state</option> the OS tree is |
763 | 764 | mounted read-only, but <filename>/var</filename> is mounted as |
764 | 765 | <literal>tmpfs</literal> instance into it (the system thus |
765 | 766 | starts up with read-only OS resources and configuration, but |
766 | 767 | pristine state, any changes to the latter are lost on |
767 | 768 | shutdown). When the mode parameter is specified as |
768 | | - <literal>no</literal> (the default) the whole OS tree is made |
| 769 | + <option>no</option> (the default) the whole OS tree is made |
769 | 770 | available writable.</para> |
770 | 771 |
|
771 | | - <para>Note that setting this to <literal>yes</literal> or |
772 | | - <literal>state</literal> will only work correctly with |
| 772 | + <para>Note that setting this to <option>yes</option> or |
| 773 | + <option>state</option> will only work correctly with |
773 | 774 | operating systems in the container that can boot up with only |
774 | 775 | <filename>/usr</filename> mounted, and are able to populate |
775 | 776 | <filename>/var</filename> automatically, as |
776 | 777 | needed.</para></listitem> |
777 | 778 | </varlistentry> |
778 | 779 |
|
| 780 | + <varlistentry> |
| 781 | + <term><option>--settings=</option><replaceable>MODE</replaceable></term> |
| 782 | + |
| 783 | + <listitem><para>Controls whether |
| 784 | + <command>systemd-nspawn</command> shall search for and use |
| 785 | + additional per-container settings from |
| 786 | + <filename>.nspawn</filename> files. Takes a boolean or the |
| 787 | + special values <option>override</option> or |
| 788 | + <option>trusted</option>.</para> |
| 789 | + |
| 790 | + <para>If enabled (the default) a settings file named after the |
| 791 | + machine (as specified with the <option>--machine=</option> |
| 792 | + setting, or derived from the directory or image file name) |
| 793 | + with the suffix <filename>.nspawn</filename> is searched in |
| 794 | + <filename>/etc/systemd/nspawn/</filename> and |
| 795 | + <filename>/run/systemd/nspawn/</filename>. If it is found |
| 796 | + there, its settings are read and used. If it is not found |
| 797 | + there it is subequently searched in the same directory as the |
| 798 | + image file or in the immediate parent of the root directory of |
| 799 | + the container. In this case, if the file is found its settings |
| 800 | + will be also read and used, but potentially unsafe settings |
| 801 | + are ignored. Note that in both these cases settings on the |
| 802 | + command line take precendence over the corresponding settings |
| 803 | + from loaded <filename>.nspawn</filename> files, if both are |
| 804 | + specified. Unsafe settings are considered all settings that |
| 805 | + elevate the container's privileges or grant access to |
| 806 | + additional resources such as files or directories of the |
| 807 | + host. For details about the format and contents of |
| 808 | + <filename>.nspawn</filename> files consult |
| 809 | + <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> |
| 810 | + |
| 811 | + <para>If this option is set to <option>override</option> the |
| 812 | + file is searched, read and used the same way, however the order of |
| 813 | + precedence is reversed: settings read from the |
| 814 | + <filename>.nspawn</filename> file will take precedence over |
| 815 | + the corresponding command line options, if both are |
| 816 | + specified.</para> |
| 817 | + |
| 818 | + <para>If this option is set to <option>trusted</option> the |
| 819 | + file is searched, read and used the same way, but regardless |
| 820 | + if found in <filename>/etc/systemd/nspawn/</filename>, |
| 821 | + <filename>/run/systemd/nspawn/</filename> or next to the image |
| 822 | + file or container root directory, all settings will take |
| 823 | + effect, however command line arguments still take precedence |
| 824 | + over corresponding settings.</para> |
| 825 | + |
| 826 | + <para>If disabled no <filename>.nspawn</filename> file is read |
| 827 | + and no settings except the ones on the command line are in |
| 828 | + effect.</para></listitem> |
| 829 | + </varlistentry> |
| 830 | + |
779 | 831 | <xi:include href="standard-options.xml" xpointer="help" /> |
780 | 832 | <xi:include href="standard-options.xml" xpointer="version" /> |
781 | 833 | </variablelist> |
|
859 | 911 | <title>See Also</title> |
860 | 912 | <para> |
861 | 913 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
| 914 | + <citerefentry><refentrytitle>systemd.nspawn</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
862 | 915 | <citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
863 | 916 | <citerefentry project='mankier'><refentrytitle>dnf</refentrytitle><manvolnum>8</manvolnum></citerefentry>, |
864 | 917 | <citerefentry project='die-net'><refentrytitle>yum</refentrytitle><manvolnum>8</manvolnum></citerefentry>, |
|
0 commit comments