I can't quite reproduce this information. Could you show the container
configuration?
Note that your host being trusty (and presumably upstart-based), if your
container also is running upstart, then if you use --share-net 1, then
the abstract unix socket which upstart uses to ask init to shut down
will be talking in the host's network, to the host's upstart.
--share-net 1 is not recommended. It is similar to 'lxc.network.type =
none', of which lxc.container.conf(5) warns:
none: will cause the container to share the host's network
namespace. This means the host network devices are usable in the container. It
also means that if both the container and host have upstart as init, 'halt' in a
container (for instance) will shut down the host.
--
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
--
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
