[lxc-devel] [PATCH 2/2] lxc.container.conf: document the type: lxc.rootfs conventions

[Serge Hallyn]

Quoting Michael H. Warfield (mhw at WittsEnd.com):
> On Thu, 2014-05-15 at 14:33 +0000, Serge Hallyn wrote:
> > Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
> > ---
> >  doc/lxc.container.conf.sgml.in | 14 ++++++++++++++
> >  1 file changed, 14 insertions(+)
> 
> > diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in
> > index 6e96889..39de1cc 100644
> > --- a/doc/lxc.container.conf.sgml.in
> > +++ b/doc/lxc.container.conf.sgml.in
> > @@ -876,6 +876,20 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
> >  	      specified, the container shares its root file system
> >  	      with the host.
> >  	    </para>
> > +	    <para>
> > +          For directory or simple block-device backed containers,
> > +          a pathname can be used.  If the rootfs is backed by a nbd
> > +          device, then <filename>nbd:file:1</filename> specifies that
> > +          <filename>file</filename> should be attached to a nbd device,
> > +          and partition 1 should be mounted as the rootfs.
> > +          <filename>nbd:file</filename> specifies that the nbd device
> > +          itself should be mounted.  <filename>overlayfs:/lower:/upper</filename>
> > +          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
> > +          <filename>/file</filename> to a loop device and mount the loop device.
> > +	    </para>
> >  	  </listitem>
> >  	</varlistentry>
> >  
> > -- 
> > 1.9.1
> 
> I may be off base here but, does this relate to that exchange on the
> -users list a couple of weeks ago about the Fedora template and an lvm
> backing store?

No, don't really recall that exchange.

> Or is that one of these "simple block-device backed"
> things?  The OP never got back with us and I haven't tried testing it
> myself.

Not sure what you are referring to.  This is just something that is nice
to have so that users can download a qcow2 image like
http://cloud-images.ubuntu.com/utopic/current/utopic-server-cloudimg-amd64-disk1.img
and use it without having to convert it.