apt-get upgrade on Ubuntu 20.04 box fails because there is not enough space in /boot #294
Comments
evgeni
added a commit
to evgeni/forklift
that referenced
this issue
Jan 26, 2024
for some reason /boot contains both initrds with and without .img even if the ones with are not used, however, as /boot space is limited they prevent upgrades of packages, failing our pipelines delete them we don't really care about new kernels, or rebooting those VMs, but we care about updated userland, and this prevents it See lavabit/robox#294 for details
evgeni
added a commit
to theforeman/forklift
that referenced
this issue
Jan 26, 2024
for some reason /boot contains both initrds with and without .img even if the ones with are not used, however, as /boot space is limited they prevent upgrades of packages, failing our pipelines delete them we don't really care about new kernels, or rebooting those VMs, but we care about updated userland, and this prevents it See lavabit/robox#294 for details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ohai,
I've tested this on the following boxes, but I think others could be affected too:
When you boot the machine, you see there are at least two kernels installed:
Additionally, the initrds are doubled:
initrd.img-5.4.0-169-genericandinitrd.img-5.4.0-169-generic.img(and same for -42-). However, the ones ending in.imgare not referenced from thegrub.cfgat all:Calling
apt-get update && apt-get upgraderesults in:Calling
rm -f /boot/*-generic.imgbefore doing the upgrade cleans up enough space to not break things.I think two optimizations can be made:
.imgfiles (wherever they come from)The text was updated successfully, but these errors were encountered: