This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu26
---
lxc (0.8.0~rc1-4ubuntu26) quantal; urgency=low
* 0100-template-cleanup-cache: clean up template cache if interrupted
during build. (LP: #1037331)
* 0101-template-empty-apt-cache: do an apt-cache clean after
** Summary changed:
- lxc-start exits success on failure when non-root
+ lxc-start exits success on failure when non-root in daemon mode
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Ok, I'm actually not sure what we should do about this.
'-d' doesn't just mean don't show a console, it means daemonize. It
does this by calling daemon(3), which forks(), lets the child continue,
and exits success.
We could toss extra checks in before the call to daemon(3) to check for
--
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:
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
Indeed that should be fixed. Thanks for the bug report.
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
