Purging the custom kernel does not remove initramfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-aws (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
linux-kvm (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Purge the kernel and you will be left with the initramfs in /boot and /var/lib/
* Launch a bionic/cosmic AWS image
* Purge the kernel
$ sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs*
$ ls /boot/
grub initrd.
$ ls /var/lib/
4.15.0-1021-aws
This was seen with Bionic and Cosmic with linux-aws and linux-kvm
Impact: during cloud image builds we remove one kernel and install the optimized kernel like linux-aws. The missing cleanup consumes disk space for images that are meant to be small; it also surfaces a latent bug in initramfs-tools where mkinitramfs will attempt to run to update every initramfs in /var/lib/
summary: |
- Purging the kernel does not remove initramfs + Purging the custom kernel does not remove initramfs |
A few questions:
- Could you please provide the output of the apt-get purge call?
- If update-initramfs is called in it, could you please manually call it with the verbose flag (-v) and attach the output?
- Does this only happen on the half-configured scenario?
I'm moving the status to Incomplete. Please feel free to move it back to New as soon as new information is available.