Bug#934387: lxc: privileged LXC container do not start

2019-08-26 Thread Diego Torres
> Yes, now update to the version claiming fixing the issue, that is > 1:3.1.0+really3.0.4-2. If you then see still similar or same issue > might you post your debug log output, which might help further > investigating the issue. I have updated liblxc1 with containers running. Containers where stop

Bug#934387: lxc: privileged LXC container do not start

2019-08-26 Thread Salvatore Bonaccorso
Hi Diego, [adding bug back for tracking the progress] On Mon, Aug 26, 2019 at 09:55:10PM +0200, Diego Torres wrote: > I have downgraded and rebooted, and now the containers are working ok with > 3-8. I believe I have tested all the possible combinations. > > Should I upgrade to 4-2 with contain

Bug#934387: lxc: privileged LXC container do not start

2019-08-26 Thread Salvatore Bonaccorso
Hi Diego, On Mon, Aug 26, 2019 at 09:37:13PM +0200, Diego Torres wrote: > Hi Salvatore, > > I'm having the exact same problem that you reported. Also tested with > "lxc.apparmor.profile = unconfined" with other container, with no success. > > Also, downgrading to1:3.1.0+really3.0.3-8 allows the

Bug#934387: lxc: privileged LXC container do not start

2019-08-26 Thread Diego Torres
Hi Salvatore, I'm having the exact same problem that you reported. Also tested with "lxc.apparmor.profile = unconfined" with other container, with no success. Also, downgrading to1:3.1.0+really3.0.3-8 allows the containers to start again. Latest report said that bug was fixed with 1:3.1.0+really

Bug#934387: [pkg-lxc-devel] Bug#934387: lxc: privileged LXC container do not start: ERROR cgfsng - cgroups/cgfsng.c:__do_cgroup_enter:1498 - No space left on device - Failed to enter cgroup "/sys/fs/c

2019-08-10 Thread Salvatore Bonaccorso
Hi Thanks for your followup here and those on IRC: On Sat, Aug 10, 2019 at 09:59:17PM +0200, Pierre-Elliott Bécue wrote: > I'll follow up to github to ask for some help, but have you tried to > debug the "no space left on device" part? Are cgroups properly > available? Not on the first, but cgro

Bug#934387: [pkg-lxc-devel] Bug#934387: lxc: privileged LXC container do not start: ERROR cgfsng - cgroups/cgfsng.c:__do_cgroup_enter:1498 - No space left on device - Failed to enter cgroup "/sys/fs/c

2019-08-10 Thread Pierre-Elliott Bécue
Le samedi 10 août 2019 à 16:59:32+0200, Salvatore Bonaccorso a écrit : > Package: lxc > Version: 1:3.1.0+really3.0.4-1 > Severity: normal > > Hi > > After an update of lxc and liblxc1 to 1:3.1.0+really3.0.4-1 privileged > container do not start anymore on an affected host (this might be a > probl

Bug#934387: lxc: privileged LXC container do not start: ERROR cgfsng - cgroups/cgfsng.c:__do_cgroup_enter:1498 - No space left on device - Failed to enter cgroup "/sys/fs/cgroup/cpuset//lxc.monitor/te

2019-08-10 Thread Salvatore Bonaccorso
Hi FWIW, I bootstraped a minimal VM running buster then: apt-get --no-install-recommends install lxc-templates lxc debootstrap rsync and created lxc-create -n test-container -t debian -- -r sid The container start here with 1:3.1.0+really3.0.3-8. The updated the VM to unstable including the lx

Bug#934387: lxc: privileged LXC container do not start: ERROR cgfsng - cgroups/cgfsng.c:__do_cgroup_enter:1498 - No space left on device - Failed to enter cgroup "/sys/fs/cgroup/cpuset//lxc.monitor

2019-08-10 Thread Salvatore Bonaccorso
Package: lxc Version: 1:3.1.0+really3.0.4-1 Severity: normal Hi After an update of lxc and liblxc1 to 1:3.1.0+really3.0.4-1 privileged container do not start anymore on an affected host (this might be a problem specific, but not entirely sure if it is a bug in the package or it's here a user erro