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 containers to start > again. > > Latest report said that bug was fixed with 1:3.1.0+really3.0.4-1.1. I can > confirm that neither 4-1.1 nor 4-2 fixes the problem. After an apt-get > upgrade using testing/unstable, with the following versions: > > liblxc1 1:3.1.0+really3.0.4-2 > libpam-cgfs 1:3.1.0+really3.0.4-2 > lxc 1:3.1.0+really3.0.4-2 > lxcfs 3.0.4-2 > python3-lxc 1:3.0.4-1 > > Could someone verify that it is working with 4-2?
yes it fixes the issue for me both with -1.1 as the followup. Did you maybe encounter the same problem I had https://github.com/lxc/lxc/issues/3118#issuecomment-521284904 ? The system seems to be in bad state once the broken version was installed. But having a fresh reboot with the old version 1:3.1.0+really3.0.3-8 then upgrading to the fixed one directly did not show anymore the issue. Do you independly on the above see the same problem? If so it might be worth to open an new issue in upstream issue tracker. Regards, Salvatore
