Interesting, so apparently only the lxc monitor itself is hung. could
you please strace that process (it will be the parent of the container
init) so we can see what it is hung trying to do?
Did you happen to upgrade lxc to a significantly newer version after
starting the container? I don't know of any changes we've made to the
monitor protocol, but it's not impossible.
Can you give more details about how you set up your custom container?
Is this (somewhat - i.e. you can do it more than once even if not
always) reproducible with a precise set of steps?
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
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
