proxmox-mirrors/mirror_lxc
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_lxc synced 2025-07-11 09:04:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

lxc.container.conf(5): update guidance for lxc.mount.entry mount target

Browse Source 
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:
Serge Hallyn 2014-05-16 10:14:16 -04:00
parent 3abd3e54eb
commit 6191f4f421
1 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/lxc.container.conf.sgml.in
View File

@ -672,13 +672,21 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
<para>
specify a file location in
the <filename>fstab</filename> format, containing the
mount information. If the rootfs is an image file or a
block device and the fstab is used to mount a point
somewhere in this rootfs, the path of the rootfs mount
point should be prefixed with the
<filename>@LXCROOTFSMOUNT@</filename> default path or
the value of <option>lxc.rootfs.mount</option> if
specified. Note that when mounting a filesystem from an
mount information. The mount target location can and in
most cases should be a relative path, which will become
relative to the mounted container root. For instance,
</para>
<screen>
proc proc proc nodev,noexec,nosuid 0 0
</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)
cannot be auto as with
<citerefentry>