** Branch linked: lp:~jibel/ubuntu/raring/flash-
kernel/skip_inside_lxc_container
--
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/1160360
Title:
flash-kernel failed in an armhf lxc
Moving to flash-kernel
LXC do not rootfs modifications from the templates. The proposed fix in
attached branch do the equivalent of then environment variable
FLASH_KERNEL_SKIP and skips flash-kernel run inside LXC container by checking
the result of 'running-in-container'
** Package changed:
This is interesting - thanks Jean-Baptiste.
So do we need to:
- Not have a kernel image package installed in the container in the first
place?
- Arrange for flash-kernel not to be run inside a container (kernel postinst?
update-initramfs postinst?)?
- Make flash-kernel depend on
It is even more annoying because if you specify apt_upgrade: true in a
cloud-config script and there is a package that triggers kernel hooks,
then it breaks the provisioning of the lxc guest.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
it breaks even without that directive.
Another test case to run on a day with a package upgrade that will run
kernel hooks
1. Create the user-data file with the following content:
88888
#cloud-config
locale: en_US.UTF-8
password: ubuntu
chpasswd: {
@Robie: The right solution here is to do the same hack we have in grub,
which is to using running-in-container to detect LXC and skip that
part of the code.
/etc/kernel/postinst.d/zz-update-grub can be used as an example for that
change if you're interested in fixing this issue yourself.
I'm
Jean-Baptiste kindly tested this attached change, but it didn't work. He
said that it still broke in the initramfs-tools postinst as it did
before.
But I wonder - why is flash-kernel installed at all in the cloud images?
Can we fix this by not including flash-kernel at all?
** Patch added: