Hi Xavier, On Thu, May 19, 2016 at 01:27:58PM +0200, Xavier Quost wrote: > Sorry for this late answer.
No worries, my time is limited too and I also answer slowly ;) > > Could you still provide stippets of auth.log and messages around that > > time? Just to crosscheck. [ nothing suspicious ] > > Do you mean you have other Jessie systems where libpam-cgfs does not > > trigger this behaviour? > Yes, but on those systems, there was no attempt to install lxc > > > Do you by any chance have SELinux or AppArmor enabled on these boxes? > Yes, apparmor comes as a requirement of lxc It's only a recommends (and was even droped to suggests in Sid now). You can safely deinstall it. Does that change anything? > What would be the following steps ? I'm still trying to reproduce this in my setup, but can't :/ So far I have tried the following combinations: jessie + libpam-cgfs 2.0 jessie + libpam-cgfs 2.0 + lxc 2.0 + lxcfs 2.0 jessie + libpam-cgfs 2.0 + lxc 2.0 + lxcfs 2.0 + apparmor jessie + libpam-cgfs 2.0 + lxc 2.0 + lxcfs 2.0 + apparmor + linux-image-4.5 jessie + libpam-cgfs 2.0 + lxc 2.0 + lxcfs 2.0 + apparmor + linux-image-4.5 + cgroup-* all of them allow ssh and console logins for root and a user just fine. Any pointers how to reproduce your setup would be awesome. Greets Evgeni