Cloudron Forum

@zjuhasz1 Right, this is also fixed. The packages were installed because we use apt without --no-install-recommends. You can remove those gnome packages by hand for now if it bothers you but it doesn't run any daemons, so it's mostly harmless.

@robi @nebulon Thank you. I will try the recipe I found at Stack Exchange and then report back. In my situation it is for a home server. So I can easily connect a keyboard and monitor to enter the encryption password on the drive in the wake of a server reboot. I do want to be able to do it remotely though if I'm not home. But the situation is not urgent for me. That explains my delay in following through. But I will.

@necrevistonnezr Don't upgrade yet, I have a blog post that I will publish later today on how to update. It's a bit different than 16 to 18. That main difference is that the mysql server has to be upgraded as well.

@girish I successfully migrated my Cloudron from one server to another. I followed your directions and updated Cloudron to v 6.0.0 before making my final backup of the old server. Thank you.

@mehdi you're right, my poor choice of words.. apt is a binary that can call libapt-pkg libraries and provides a subset of interactive options and commands for apt-get/cache by default. apt-get is not limited to those options.

Are you telling me that apt install screen is going to break updates?

@d19dotca I think the -f flag on install just "cleans up" the installation : it notices that some files required for some packages were removed (in the previous line), so it removes said packages. What actually frees up the space is the rm. The apt-get -f install just makes the system notice that the packages in question are not installed anymore

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

Thanks @girish Can't hardly expect it

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.