Thanks for reporting this bug. I can't reproduce anything with lxc-destroy. lxc-destroy on a running container gives me
ubuntu@server-6896fdb5-46e0-47f9-b547-0a841dbf4c75:~$ sudo lxc-destroy -n r1 lxc-destroy: 'r1' state: RUNNING; aborted lxc-info tries to talk to the container-specific monitor, so my suspicion is something went wrong in lxc-start itself (not related to lxc-destroy). lxc-start is the one which runs the monitor, so lxc-info would find the unix domain socket existing, try to connect, and hang while waiting for a repsonse. Still testing. -- 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/1177583 Title: lxc-list crash after lxc-destory of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+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
