mirror of
https://git.proxmox.com/git/mirror_lxc
synced 2025-07-11 19:39:50 +00:00
lxc.container.conf(5): update guidance for lxc.mount.entry mount target
For years it has been best practice to use a relative path as the mount target. But the manpage hasn't reflect that. Fix it. Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com> Acked-by: Dwight Engen <dwight.engen@oracle.com>
This commit is contained in:
parent
3abd3e54eb
commit
6191f4f421
@ -672,13 +672,21 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
|
|||||||
<para>
|
<para>
|
||||||
specify a file location in
|
specify a file location in
|
||||||
the <filename>fstab</filename> format, containing the
|
the <filename>fstab</filename> format, containing the
|
||||||
mount information. If the rootfs is an image file or a
|
mount information. The mount target location can and in
|
||||||
block device and the fstab is used to mount a point
|
most cases should be a relative path, which will become
|
||||||
somewhere in this rootfs, the path of the rootfs mount
|
relative to the mounted container root. For instance,
|
||||||
point should be prefixed with the
|
</para>
|
||||||
<filename>@LXCROOTFSMOUNT@</filename> default path or
|
<screen>
|
||||||
the value of <option>lxc.rootfs.mount</option> if
|
proc proc proc nodev,noexec,nosuid 0 0
|
||||||
specified. Note that when mounting a filesystem from an
|
</screen>
|
||||||
|
<para>
|
||||||
|
Will mount a proc filesystem under the container's /proc,
|
||||||
|
regardless of where the root filesystem comes from. This
|
||||||
|
is resilient to block device backed filesystems as well as
|
||||||
|
container cloning.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
Note that when mounting a filesystem from an
|
||||||
image file or block device the third field (fs_vfstype)
|
image file or block device the third field (fs_vfstype)
|
||||||
cannot be auto as with
|
cannot be auto as with
|
||||||
<citerefentry>
|
<citerefentry>
|
||||||
|
Loading…
Reference in New Issue
Block a user