Quoting Christian Brauner (christianvanbrau...@gmail.com): > Explain that multiple /lower layers can be used. > > Signed-off-by: Christian Brauner <christian.brau...@mailbox.org>
Acked-by: Serge E. Hallyn <serge.hal...@ubuntu.com> > --- > doc/lxc.container.conf.sgml.in | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in > index 18ad924..17a027a 100644 > --- a/doc/lxc.container.conf.sgml.in > +++ b/doc/lxc.container.conf.sgml.in > @@ -1036,7 +1036,9 @@ proc proc proc nodev,noexec,nosuid 0 0 > specifies that the rootfs should be an overlay with > <filename>/upper</filename> > being mounted read-write over a read-only mount of > <filename>/lower</filename>. > <filename>aufs:/lower:/upper</filename> does the same using aufs > in place > - of overlayfs. <filename>loop:/file</filename> tells lxc to attach > + of overlayfs. For both <filename>overlayfs</filename> and > + <filename>aufs</filename> multiple <filename>/lower</filename> > + directories can be specified. <filename>loop:/file</filename> > tells lxc to attach > <filename>/file</filename> to a loop device and mount the loop > device. > </para> > </listitem> > -- > 2.7.0 > > _______________________________________________ > lxc-devel mailing list > lxc-devel@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-devel _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
