libpam-cgfs fails to create freezer cgroup writable by user

[James Tocknell]

This is on 16.04.6.

It appears that on some systems, libpam-cgfs doesn't set the correct cgroup information, which prevents containers from starting. This can be seen by looking at the contents of /proc/self/cgroup, which in my case was:
blkio:/user.slice
cpu,cpuacct:/user.slice
cpuset:/
devices:/user.slice
freezer:/
hugetlb:/
memory:/user.slice
name=systemd:/user.slice/user-18160.slice/session-12214.scope
net_cls,net_prio:/
perf_event:/
pids:/user.slice/user-18160.slice

whereas it should have instead of freezer:/ freezer:/user/<myusername>/0

[Stéphane Graber (stgraber)]

How are you logging in and can you confirm that this path does hit libpam_cgfs?
Also look in /var/log/auth.log for potential errors.