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 (
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525787/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525786/+files/KernLog.txt
--
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/152
apport information
** Attachment added: "lxc-net.default.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525788/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525785/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "lxc.default.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525789/+files/lxc.default.txt
--
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/
apport information
** Attachment added: "lxcsyslog.txt"
https://bugs.launchpad.net/bugs/1520225/+attachment/4525790/+files/lxcsyslog.txt
--
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
Public bug reported:
Hi,
Earlier today, a server got powered off and I'm 99% sure it's because I ran the
following command as root :
# lxc-stop -n
The container was started manually with :
# lxc-start -n -F --share-net 1
and it wasn't fully booted (ie I didn't have the console yet).
syslog
Also : would running "maas-region-admin edit_named_options --migrate-
conflicting-options" without "forwarders" in named.conf.options remove
the forwarder setting from the MAAS database ?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
Hi Serge, Martin,
As Serge mentioned in #4, this bug will cause breakage if using both "ip
netns" and lxc. As I'm sure you're aware, the OpenStack neutron/quantum
gateway makes heavy use of the "ip netns" feature, and it's valid to
have LXC containers on the server hosting tje quantum gateway.
Gi
10 matches
Mail list logo