[lxc-devel] Unprivileged containers don't start with lxcfs 2.0.0

[Serge Hallyn]

Quoting Mathias Gibbens (mathias at calenhad.com):
> On Tue, 2016-04-05 at 16:45 +0000, Mathias Gibbens wrote:
> > On Tue, 2016-04-05 at 14:59 +0000, Serge Hallyn wrote:
> > > Quoting Mathias Gibbens (mathias at calenhad.com):
> > > > On Sat, 2016-04-02 at 15:53 +0000, Serge Hallyn wrote:
> > > > > Quoting Mathias Gibbens (mathias at calenhad.com):
> > > > > >   This evening I upgraded my lxc/lxcfs install, seeing as how lxcfs
> > > > > > 2.0.0 was tagged earlier today. However, with the current lxcfs (2.0.0)
> > > > > > my unprivileged containers fail to start:
> > > > > > 
> > > > > > > lxc at narya:~$ lxc-start -F -n aule.calenhad.com
> > > 
> > > Which lxc version is this.  What pkg source specifically.
> > 
> >   This is lxc 2.0.0.rc15 compiled directly from the release source at
> > https://github.com/lxc/lxc/archive/lxc-2.0.0.rc15.tar.gz. The configure
> > command I've been using is
> > 
> > > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-init-script=systemd --enable-doc --enable-apparmor --enable-seccomp --enable-capabilities --enable-cgmanager --enable-python

note lxcfs no longer uses cgmanager, so '--enable-cgmanager' isn't needed.  It
shouldn't break anything though.

> > 
> >   I have also been compiling lxcfs from source as well. I had been running lxcfs 2.0.0.beta1 before jumping to the 2.0.0 release. I haven't had time to try any of the in-between rc's to further pinpoint where things broke.
> 
>   I've spent some time trying to pinpoint where lxcfs broke, at least

In what way does it break exactly?  Can you git-bisect to a commit?