Another (likely related) issue, after using sudo to start the container, observe:
$ lxc-ls lv1 $ sudo lxc-start -n lv1 -d $ lxc-ls lv1 /usr/bin/lxc-ls: line 35: cd: /sys/fs/cgroup/cpuset///lxc: Permission denied ls: cannot access lv1: No such file or directory $ sudo lxc-ls lv1 lv1 $ sudo lxc-list RUNNING lv1 STOPPED So, as it is now after starting the container 'sudo lxxc-ls' shows 2 containers, but 'lxc-ls' (without sudo) shows annoying messages. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/918327 Title: lxc-start exits success on failure when non-root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/918327/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
