Ah we did hit that kernel/initramfs issue with /boot getting filled up by Ubuntu already before. If it is 100% full even the autoremove fails. Would be good to actually not just maybe warn about that, but see how the whole situation can be mitigated in the first place. Afterall it is not much use to have that many kernel versions around.

@girish & @marcusquinn thanks for the hints! Finally the AWS guide did the trick, it was a 2 step approach (in my case): sudo growpart /dev/sda 3 sudo resize2fs /dev/sda3

It's planned but I have no ETA - https://git.cloudron.io/cloudron/box/-/issues/684 . We need a proper fix for https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1872281 which was the blocker (collectd unable to load python plugins which we use for the graphs).

As @scooke and @mehdi already mentioned, the sole reason to support only one distribution is the reduced complexity by having to deal with only a single well known system. Even different ubuntu versions require quite a lot of testing and different code. Sometimes package names change for example. We essentially just settled on Ubuntu 16.04 initially since that was available on basically every VPS provider. Really that is the main concern for us. Naturally for security updates we then progressed to 18.04 and will soon hopefully support 20.04. Other distros with even other package managers are simply just overhead and cause trouble to users. In the end from what Cloudron requires, there will hardly be any noticeable difference in speed or resources use between any of the distros, so we lean towards stability here.

I remember some cleanup features in the unattended-upgrades package.

Good point, I thought this would be triggered by the security update job from ubuntu already, but apparently not.

Nice, thanks @girish

Thanks all! I just installed it on 1 of my Cloudron servers (at DO) to see and experience if and how it works.