[lxc-users] lxd not using cgmanager but cgfs instead

Hi, Is is normal for lxd to use cgfs and not cgmanager? I can tell it's using cgfs based on the log line: lxc 1455545499.588 WARN lxc_cgfs - cgfs.c:lxc_cgroup_get_container_info:1100 - Not attaching to cgroup hugetlb unknown to /var/lib/lxd/containers centos I'm very much clueless

Re: [lxc-users] Missing /proc/self after lxc-attach ?

> On February 15, 2016 at 1:29 PM Mateusz Korniak > wrote: > [1]: After lxc-attach entry to container: > # ls -la /proc/self > ls: cannot read symbolic link /proc/self: No such file or directory > lrwxrwxrwx 1 root root 0 Feb 15 12:05 /proc/self What is the exact

Re: [lxc-users] Missing /proc/self after lxc-attach ?

On Mon, Feb 15, 2016 at 7:29 PM, Mateusz Korniak < mateusz-li...@ant.gliwice.pl> wrote: > Hi ! > I am facing problem that > /proc/self > is missing after I enter container via lxc-attach. [1] > > When I log in to same container via lxc-start -F console, everything looks > OK. > [2] > > Is it bug

[lxc-users] Missing /proc/self after lxc-attach ?

Hi ! I am facing problem that /proc/self is missing after I enter container via lxc-attach. [1] When I log in to same container via lxc-start -F console, everything looks OK. [2] Is it bug or feature? It reduces usability of lxc-attach as many apps like top [3] and dynamic linking via