Re: [lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

This problem is related to network-manager (NM) or systemd. I tried to disable NM but I couldn't. NM started with every boot (does systemd depend on it?). I switched to upstart. Now NM is down, lxcbr0 starts up. Everything works as it used to be including my routes and dns servers. 2015-10-26

Re: [lxc-users] set "lxc.aa_allow_incomplete = 1" - where do I add it for lxd?

Thanks, it worked. How do I set other "lxc-style" values in lxd, like for example: lxc.network.ipv4 = 10.0.12.2/24 lxc.network.ipv4.gateway = 10.0.12.1 lxc.network.ipv6 = :::::55 lxc.network.ipv6.gateway = :2345:6789:::2 Same "lxc config set containername", i.e.: lxc

[lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

zoolook@venkman:~$ LC_ALL=C ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found zoolook@venkman:~$ LC_ALL=C sudo service lxc-net start zoolook@venkman:~$ LC_ALL=C ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found zoolook@venkman:~$

[lxc-users] re lxcbr0 doesn't exist after upgrade to 15.10

Norberto Great coincidence as I read your msg to the lxc-users list about the lxcbr0 bridge disappearing after upgrade to Ubuntu 15.10. I just finished upgrading one of my machines to 15.10 this weekend and today I noticed I couldn't start any containers. Then I noticed there is no lxcbr0 any

Re: [lxc-users] lxcbr0 doesn't exist after upgrade to 15.10

On Tue, Oct 27, 2015 at 6:20 AM, Norberto Bensa wrote: > This problem is related to network-manager (NM) or systemd. > > I tried to disable NM but I couldn't. NM started with every boot (does > systemd depend on it?). I switched to upstart. Now NM is down, lxcbr0 >

Re: [lxc-users] Container doesn't connect to bridge

I already have networking setup in the container: root@thinkweb:/# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.54.110 netmask 255.255.255.128 gateway 192.168.54.1 When I add lxc.network.ipv4.gateway to the config it now works.

[lxc-users] set "lxc.aa_allow_incomplete = 1" - where do I add it for lxd?

I get the following when starting a container with lxd: Incomplete AppArmor support in your kernel If you really want to start this container, set lxc.aa_allow_incomplete = 1 in your container configuration file Where exactly do I set this with lxd? I don't really see a