@benborges Ah ok. Maybe you can wait for 7.3. Please update to that and try to update again and we can debug further. There are some cgroup v2 related fixes for Ubuntu 22 in 7.3 which affect docker container creation, it's possible you hit that case.

@bubonicfred said in Submit Cloudron to Ubuntu for Publication:

You can install snapd on non-ubuntu systems. Though I have no idea if they have any advantage over flatpak or appimage.

Yep, except it turns that we want to get away from snap instead of adopting it for some reasons mentioned here above, so well that's a choice 😉

@humptydumpty I think not - https://askubuntu.com/questions/844689/instance-with-canonical-livepatch-service-requires-restart

@necrevistonnezr said in Nextcloud App "not responding" after upgrading to Ubuntu 22.04:

EDIT: I guess that replacement should go into /home/yellowtent/box/src/infra_version.js - but after a restart of box, still not running...

Yes, that's the correct place to fix it!

I will add a warning to our docs that updating to ubuntu 22 when using FTS feature does not work out of the box / without patching until 7.3.

@robi said in Best way to update from Ubuntu 18.04 to 20.04?:

one can use the -y option for apt to 'assume yes' to all prompts.

this doesn't work with do-release-upgrade for whatever reason.

@girish perfect - that fixed that! now bumping to 7.2 - thanks mate

@girish it does, yes. They also have a KVM style one for their "elastic metal" service. I'll give this a try and report back. My main question is whether I can install the OS from an image or if I have to use one of theirs. Otherwise, I may have to find another host 🙂

@humptydumpty thanks for the hint. I have update the blog post accordingly.

Regarding the Ubuntu installation, you can already set the server name to the intended dashboard domain and for the username, just use ubuntu or anything besides cloudron-* or yellowtent, to avoid conflict and confusion later.

@matthewdykstra Cloudron actually does do upgrades for you. If you check the notifications from time to time, at my.example.com/#/notifications, there will be some in there that say some upgrades have taken place and that the machine needs to be restarted. So, the security upgrades that @girish mentions DO happen, just automatically. You don't need to worry that your server will be sitting there becoming increasingly weak and exposed.

The upgrade guides should mostly be identical for upgrading Ubuntu. The Cloudron guide has maybe couple of additional notes/configuration for making sure things are running after upgrade. What error are you hitting when upgrading following either of the docs? I suspect they hit the same error.

@matthewdykstra I don't need an account. Thanks for testing.

thanks for proving my point that one cannot have a discussion with you 🙂

Don't use Strato.
At first glance they seem like a good hoster, but they are not. Even if their pricing model seems competitive.
For basic stuff like a single Wordpress or something it might be fine, but I would not entrust them my systems.

I had so many customers throwing Strato out of the window in a fit of rage.

Just my personal opinion based on what I have witnessed.

My understanding is that mint is primarily targeting a Desktop environment.

@subtlecourage I'm not sure on which machine you get this message now, but have you checked for file permissions (chmod) on your RSA keys that could also be a factor.

Andy

@ethanxrosen right, first migrate to 18 - https://docs.cloudron.io/guides/upgrade-ubuntu-18/ and then 20.

@necrevistonnezr noone is blaming you, no need to be defensive.

Discuss the technical merits of the upgrades and changes?

@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.