Quoting Serge Hallyn > Perhaps after a (reasonably long) timeout we should assume > it is dead, hard-kill the container (in this case the owner of the > command socket), and continue.
I'm seeing this behaviour happen in Vivid although in my case the "stuck" container is perfectly responsive and is working fine e.g. if I ssh into it. So the assumption that the container is dead and should be killed may not be the answer... I'd rather have the container work and lxc-ls broken than the other way around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377973 Title: lxc-destroy/lxc-stop gets stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
