[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
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
Serge, why do we offer people something which is such a landmine?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1520225
Title:
lxc-stop powered off a server
Status in lxc
Because it's needed for things like the Android container on Ubuntu
Touch, application containers on OpenWRT, ...
There are legitimate use cases for those features, those use cases just
never apply when running a full Linux distro inside the container :)
LXC used to default to sharing the netns
Hi,
container config : http://paste.ubuntu.com/13524088/
/etc/apt/sources.list.d just contains a repo for some homemade backports
"dpkg -l | grep lxc" was given in the initial comment, but here it is again :
$ dpkg -l|grep lxc
ii liblxc1 1.0.7-0ubuntu0.10 amd64 Linux Containers userspace tools
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
Please also show the output of
ls /etc/apt/sources.list.d
dpkg -l | grep lxc
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
7 matches
Mail list logo
