On Thu, Oct 22, 2015 at 02:15:18PM +, Serge Hallyn wrote:
> Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > On Thu, Oct 22, 2015 at 01:13:35PM +, Serge Hallyn wrote:
> > > Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > > > On Tue, Oct 20, 2015 at 04:17:18PM
Quoting Christian Brauner (christianvanbrau...@gmail.com):
> On Thu, Oct 22, 2015 at 01:13:35PM +, Serge Hallyn wrote:
> > Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > > On Tue, Oct 20, 2015 at 04:17:18PM +, Serge Hallyn wrote:
> > > > Quoting Christian Brauner
Quoting Christian Brauner (christianvanbrau...@gmail.com):
> On Tue, Oct 20, 2015 at 04:17:18PM +, Serge Hallyn wrote:
> > Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > > When using overlay and aufs mounts with lxc.mount.entry users have to
> > > specify
> > > absolute paths
Quoting Christian Brauner (christianvanbrau...@gmail.com):
> When using overlay and aufs mounts with lxc.mount.entry users have to specify
> absolute paths for upperdir and workdir which will then get created
> automatically by mount_entry_create_overlay_dirs() and
> mount_entry_create_aufs_dirs()
On Tue, Oct 20, 2015 at 04:17:18PM +, Serge Hallyn wrote:
> Quoting Christian Brauner (christianvanbrau...@gmail.com):
> > When using overlay and aufs mounts with lxc.mount.entry users have to
> > specify
> > absolute paths for upperdir and workdir which will then get created
> >
When using overlay and aufs mounts with lxc.mount.entry users have to specify
absolute paths for upperdir and workdir which will then get created
automatically by mount_entry_create_overlay_dirs() and
mount_entry_create_aufs_dirs() in conf.c. When we clone a container with
overlay or aufs
