Public bug reported:
The released wily image preinstalls lxc, which breaks the assumption
that lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0.3.0 when it was installed on whatever system was generating the
image. This conflicts with the network that eth0 gets attached to when
the image is brought up in a container, because it gets attached to the
host's lxcbr0, which is using 10.0.3.x.
This affects LXC, and should affect LXD but doesn't currently. (see #2)
The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a
wily host:
sudo lxc-create -t ubuntu-cloud -n wily
sudo lxc-start -n wily
sudo lxc-attach -n wily
# inside container, test connectivity, eg:
apt-get update
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: cloud-installer
--
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/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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
