From 6191f4f421b19010cfdf2606183f830c435f22cb Mon Sep 17 00:00:00 2001 From: Serge Hallyn Date: Fri, 16 May 2014 10:14:16 -0400 Subject: [PATCH] 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 Acked-by: Dwight Engen --- doc/lxc.container.conf.sgml.in | 22 +++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in index 39de1cc87..c7b36a4f0 100644 --- a/doc/lxc.container.conf.sgml.in +++ b/doc/lxc.container.conf.sgml.in @@ -672,13 +672,21 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA specify a file location in the fstab 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 - @LXCROOTFSMOUNT@ default path or - the value of 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, + + +proc proc proc nodev,noexec,nosuid 0 0 + + + 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. + + + Note that when mounting a filesystem from an image file or block device the third field (fs_vfstype) cannot be auto as with -- 2.47.2