Public bug reported:
The lxc postinst assumes that only /24 networks are used in 10.0.0.0/8.
If the host has a route for 10.0.0.2/23 (or 10.0.0.0/22, or any other
block that includes 10.0.3.0/24 or whatever other block it is checking)
then the postinst chooses a chunk of the existing network block,
breaking connectivity.
Preparing to unpack .../lxc_1.0.5-0ubuntu0.1_amd64.deb ...
Unpacking lxc (1.0.5-0ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-16) ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db (2.6.7.1-1) ...
Setting up lxc (1.0.5-0ubuntu0.1) ...
lxc start/running
Setting up lxc dnsmasq configuration.
Processing triggers for ureadahead (0.100.0-16) ...
On branch master
nothing to commit, working directory clean
-soko(root) 308 : netstat -rn | grep ^10.0..\.
10.0.2.0 10.172.64.1 255.255.254.0 UG 0 0 0 tun0
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 lxcbr0
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1358306
Title:
lxc postinst incorrectly chooses network address to use
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1358306/+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
