Quoting F Dave ([email protected]): > Turns out that it was cgroup was mounted under /cgroup, so I was able to
Yes the point of the cgfsng driver was to simplify the cgroup code by requiring now-standard cgroup mountpoints, rather than searching the system for cgroup mounts. So $controller must be mounted under /sys/fs/cgroup/$controller. THe bug (which should be fixed in git head) was that cgfsng was not failing over to cgfs.c when it did not find the required mountpoints where it expected them. > create the folder there and mount it. However the container shows the same > error: > > [root@devhost fs]# mount -t cgroup -o none,name=systemd cgroup > /cgroup/systemd/ > > [root@devhost fs]# grep cg /proc/mounts > cgroup /cgroup/cpuset cgroup rw,relatime,cpuset 0 0 > cgroup /cgroup/cpu cgroup rw,relatime,cpu 0 0 > cgroup /cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 > cgroup /cgroup/memory cgroup rw,relatime,memory 0 0 > cgroup /cgroup/devices cgroup rw,relatime,devices 0 0 > cgroup /cgroup/freezer cgroup rw,relatime,freezer 0 0 > cgroup /cgroup/net_cls cgroup rw,relatime,net_cls 0 0 > cgroup /cgroup/blkio cgroup rw,relatime,blkio 0 0 > cgroup /cgroup/systemd cgroup rw,relatime,name=systemd 0 0 > > [root@devhost fs]# lxc-start -F -n node2 > lxc-start: cgfsng.c: all_controllers_found: 431 no systemd controller > mountpoint found > lxc-start: start.c: lxc_spawn: 1079 failed initializing cgroup support > lxc-start: start.c: __lxc_start: 1329 failed to spawn 'node2' > lxc-start: lxc_start.c: main: 344 The container failed to start. > lxc-start: lxc_start.c: main: 348 Additional information can be obtained by > setting the --logfile and --logpriority options. > > > On Thu, Apr 21, 2016 at 11:38 AM, F Dave <[email protected]> wrote: > > > I cloned the master branch and rebuilt it. Did 'make uninstall' for the > > previous lxc-2.0.0 and installed new version. However it still throws the > > same error. Also tried to create the systemd folder: > > > > [root@devhost lxc]# mkdir -p /sys/fs/cgroup/systemd > > mkdir: cannot create directory `/sys/fs/cgroup/systemd': No such file or > > directory > > > > [root@devhost lxc]# ll /sys/fs/cgroup/ > > total 0 > > > > [root@devhost lxc]# ll /sys/fs/ > > total 0 > > drwxr-xr-x. 2 root root 0 Apr 21 07:07 btrfs > > drwxr-xr-x. 2 root root 0 Apr 20 09:07 cgroup > > drwxr-xr-x. 4 root root 0 Apr 21 07:07 ext4 > > drwxr-xr-x. 2 root root 0 Apr 21 07:07 selinux > > > > > > On Thu, Apr 21, 2016 at 9:14 AM, Serge Hallyn <[email protected]> > > wrote: > > > >> > cgfsng.c:all_controllers_found:431 - no systemd controller mountpoint > >> found > >> > lxc-start: cgfsng.c: all_controllers_found: 431 no systemd controller > >> > mountpoint found > >> > >> This is known. You can either run from git head to get the patch which > >> fixes this, or just make sure to have a name=systemd cgroup controller > >> mounted on the host. > >> _______________________________________________ > >> lxc-users mailing list > >> [email protected] > >> http://lists.linuxcontainers.org/listinfo/lxc-users > > > > > > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
