[Bug 1520225] Re: lxc-stop powered off a server

[Stéphane Graber]

lxc-stop didn't, upstart in your container did.

lxc-stop sends SIGPWR to the container's PID 1, in your case, upstart.
As Serge pointed out, using --share-net means that the upstart tools int
the container interact with upstart on the host.

As a result, the shutdown sequence in the container triggered some of
the host's jobs (my bet would be the rc job) which caused it to
shutdown.


To be clear, lxc-stop doesn't have any code which can cause a host shutdown on its own at all, the tool just did exactly what it usually does, send a pre-determined signal to the container's init process, it's that process which then caused the host to shutdown.

-- 
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/1520225

Title:
  lxc-stop powered off a server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1520225/+subscriptions