[lxc-users] Preparing for LXC 1.0.8

[KATOH Yasufumi]

>>> On Mon, 31 Aug 2015 13:46:01 -0400
    in message   "Re: [lxc-users] Preparing for LXC 1.0.8"
                  Stéphane Graber-san wrote:

> On Tue, Sep 01, 2015 at 03:01:07AM +1000, overlay fs wrote:
> > The bug,
> > 
> > 'Failed to whiteout' error in Trusty with 3.19 kernel
> > https://lists.linuxcontainers.org/pipermail/lxc-users/2015-August/009854.html
> > https://bugs.launchpad.net/lxc/+bug/1486073
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267
> > 
> > is present in lxc versions 1.0.7 and 1.0.8, but seems to have been resolved
> > in version 1.1.  While this bug is not stricly a regression in lxc-1.0.8,
> > the bug was latent prior to ubuntu-14.04.3 since previous 14.04.x releases
> > did not use the 3.19 kernel.

  :(snip)

> If the whiteout problem is a kernel bug, there's little we can do, if
> it's a lxc bug, then we should fix this and get the fix into the
> stable-1.0 branch.

I tried running lxc-1.0.7 on 3.19.8 kernel.

* lxc-1.0.7 with patch:
  https://github.com/lxc/lxc/commit/388db0d9ebf1b24c538a68813077b7ace31db68f
  (The module name of 3.19 kernel is "overlay". So we need this patch.)
* vanilla kernel 3.19.8 with patch:
  https://gist.github.com/tenforward/6be31831135ad942049d
  (This patch allow root in userns to mount overlayfs.)

Unpriv overlayfs container work fine.

$ uname -a
Linux enterprise 3.19.8 #2 SMP PREEMPT Wed Sep 2 17:54:50 JST 2015 x86_64 GNU/Linux
$ lxc-start --version
1.0.7
$ lxc-clone -o ct01 -n test -s -B overlayfs
Created container test as snapshot of ct01
$ lxc-start -n test -d
$ lxc-attach -n test -- apt-get update
Ign http://archive.ubuntu.com trusty InRelease
Ign http://security.ubuntu.com trusty-security InRelease
Ign http://archive.ubuntu.com trusty-updates InRelease
  :(snip)
Fetched 2244 kB in 7s (320 kB/s)                                               
Reading package lists... Done

I guess it is the bug of linux-lts-vivid kernel in Ubuntu.

I also try running HEAD of stable-1.0(1.0.8). The behavior is the
same.

Thanks,
KATOH Yasufumi