** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
lxc postinst script checks available interfaces, can choose
Status in lxc package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/
Does not affect LXD only because the LXD metadata for simple-streams is
out of date. We are going to hold off updating it until this bug is
fixed and sru'ed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
http
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
lxc postinst script checks available interfaces,
Debdiff which works for me.
I tested this by creating a cloud container, temporarily setting
USE_LXC_BRIDGE=false, rebooting, building the package, setting
USE_LXC_BRIDGE=true (leaving 10.0.3 as the lxcbr0 subnet), rebooting.
lxcbr0 comes up with 10.0.4.1 as expected. A nested trusty container
wo
** Description changed:
- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to
** Description changed:
[Problem]
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
Not sure I like this approach. An init script should never change a
system config, so this is a packaging policy violation...
To be fair, anything we come up with which picks a random/unused subnet
will still break users who may have this subnet in use behind a router,
so that's not really an opti
I don't like disabling lxc-net, because it's simpler to tell a user to
apt-get install lxd
than to
systemctl enable lxc-net
or
echo "USE_LXC_BRIDGE=true" | sudo tee -a /etc/default/lxc-net
systemctl restart lxc-net
--
You received this bug notification because you are a member of Ubuntu
Touc
Updated debdiff, which
1. stops creation of /etc/default/lxc-net on package install
2. removes that file only if upgrading from the 1.0.4ubuntu4 version with an
umodified /etc/default/lxc-net file
** Patch added: "lxcnet4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+
** Description changed:
[Problem]
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
11 matches
Mail list logo