[Bug 1671536] Re: Default initrd is LZMA compressed, yet rebuilt initramfs are gzip?

[Dan Watkins]

This is strange.  I just booted an older image and then installed a
kernel:

$ file /boot/initrd.img-4.4.0-62-generic
/boot/initrd.img-4.4.0-62-generic: LZMA compressed data, streamed
$ sudo apt update
...
$ sudo apt upgrade
...
$ file /boot/initrd.img-4.4.0-6*
/boot/initrd.img-4.4.0-62-generic: gzip compressed data, last modified: Thu Mar  9 15:48:51 2017, from Unix
/boot/initrd.img-4.4.0-66-generic: gzip compressed data, last modified: Thu Mar  9 15:49:52 2017, from Unix

I'm guessing that it comes from "--initramfs-compression lzma" on line
613 of live-build/auto/config in livecd-rootfs; I'd expect this to
translate in to some configuration in the built image, but I guess not.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1671536

Title:
  Default initrd is LZMA compressed, yet rebuilt initramfs are gzip?

Status in cloud-images:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  $ file ~/Downloads/xenial-server-cloudimg-amd64-initrd-generic
  /home/xnox/Downloads/xenial-server-cloudimg-amd64-initrd-generic: LZMA compressed data, streamed

  Yet, in the base image I don't see that initramfs config options set
  COMPRESS=lzma. Thus first boot is lzma, yet on package upgrades i
  guess initrd would be regenerated as gzip...

  Isn't the fact that all of our images use lzma and/or xz compression
  means we should switch Ubuntu default to lzma and/or xz as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1671536/+subscriptions