Closed erickeller closed 7 years ago
Thanks for reporting this issue!
From Ubuntu 16.04 to 16.10 the lxc/lxd behavior has changed with regards to networking: "lxc init" does not create lxdbr0 anymore (by default).
As a short term workaround I would suggest to create the bridge manually: lxc network create lxdbr0
edi will probably create the required bridge automatically in the future.
The new networking features of lxc 2.3+ are great: https://stgraber.org/2016/10/27/network-management-with-lxd-2-3/
Additional findings:
The playbook lxc_networking should always check if {{ edi_lxc_network_interface_name }} was brought up successfully. (Fail early and loud - otherwise a subsequent apt call will fail.)
Given the following nested container setup Ubuntu Xenial host --> Ubuntu Yakkety container --> Debian Jessie Container we hit the "5 bad udp checksums in 5 packets" error when the Jessie container tries to get the ip address using dhcp (see also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717215). As a workaround the following command can be applied within the Yakkety container: iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM --checksum-fill See also: https://github.com/lueschem/edi-ubuntu-yakkety/commit/a5167d3905bdeaaebe7448427db3f1388b3cdbe2
After some additional tests with Yakkety: When installing lxd on yakkety no lxdbr0 will get created by default. The required bridge will get created by one of the following commands: lxd init or lxc network create lxdbr0
I will improve the error message.
Environment:
Step to reproduce
The following error occurs:
This is probably done by the default configuration of the lxd package when it's installed as a dependency.