*** This bug is a duplicate of bug 1543051 ***
https://bugs.launchpad.net/bugs/1543051
This is a duplicate of bug #1543051, for which a fix has already been
uploaded and is currently in xenial-proposed.
** Changed in: sysvinit (Ubuntu)
Status: New => Invalid
** This bug has been
FWIW I dont' think this is a regression. I think this has always been
buggy. We just don't notice bc we don't generally debootstrap systems
with lxc any more.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Note that the analogous upstart test, 'initctl version', does work under
chroot
sudo lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
sudo lxc-create -t download -n x1 -- -d ubuntu -r xenial -a amd64
chroot /var/lib/lxc/t1/rootfs initctl version
init (upstart 1.12.1)
chroot
Up until last week, cloud images were being built just fine with lxc and
lxd in them, starting this week, they fail, that seems like a regression
to me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I just compared the content of lxc 1.1.5-0ubuntu6 which I'm assuming was
the last working LXC version in cloud images and lxc
2.0.0~beta2-0ubuntu2 that we have now and neither provides any
/etc/init.d script nor am I seeing any packaging change on our side
which would explain this.
Packaging diff
I'm marking the lxc task invalid as no packaging change occurred on
lxc's side and this, admittedly rare, init script configuration has been
supported for years and should still be supported.
Directly subscribing the containers team though so we can help track
down the source of the regression.
Subscribing Martin Pitt who very recently merged init-system-helpers.
I've not yet read the diff, but this seems like a fair bet as to what
changed recently (last upload was Feb 5).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Oh, good.
--
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/1543170
Title:
lxc fails to install
To manage notifications about this bug go to:
** Package changed: ubuntu => lxd (Ubuntu)
** Package changed: lxd (Ubuntu) => lxc (Ubuntu)
--
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/1543170
Title:
lxc fails to install
To
This seems very similar to bug 1185364.
--
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/1543170
Title:
lxc fails to install
To manage notifications about this bug go to:
An easy way to reproduce this is using
sudo lxc-create -t ubuntu -n x1 -- -r xenial --packages lxc
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I think the bug may be the following:
invoke-rc.d checks whether upstart or systemd is running by checking for
-d /run/systemd/system
inside the chroot, this would not be the case. Therefore it checks for
the sysvinit script, which lxc does not provide.
--
You received this bug notification
Indeed, if I do
sudo debootstrap --verbose --components=main,universe --arch=amd64
--include=lxc xenial x
pause the debootstrap after it has expanded all the packages, edit
x/usr/sbin/invoke-rc.d to change "elif test -d /run/systemd/system" on
line 278 to "elif true', then the installation
13 matches
Mail list logo
