Ubuntu 22.04 LTS (Jammy Jellyfish) Beta

[robi]

https://lists.ubuntu.com/archives/ubuntu-announce/2022-March/000278.html

https://releases.ubuntu.com/22.04/

https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

LTS for 5 years

Toolchain Upgrades
Probably mention Python 3.10 and ruby 3.0 and perl and PHP.

Security Improvements
nftables is now the default backend for the firewall.

ssh-rsa is now disabled by default in OpenSSH 31. See bug 1961833 19 to learn how to selectively re-enable it if necessary. If you are upgrading a system remotely over SSH, you should check that you are not relying on this to ensure that you will retain access after the upgrade.

scp offers a -s command line option 6 to use sftp mode rather than scp mode 10 when handling remote filenames. This new, safer, behaviour will eventually become the default.

Ubuntu Server
Ubuntu HA/Clustering
Corosync
It was updated to version 3.16 which includes some new features:

• Support for changing crypto configuration during runtime. This includes turning cryptography on or off, changing crypto_cipher and crypto_hash and also changing of crypto key.
• Default token timeout was changed from 1 seconds to 3 seconds.
  / Run corosync -v to get the list of supported crypto and compression models which can be used in corosync.conf
• Cgroup v2 support.

...

Containers runtime
containerd
It was updated to version 1.5.9. Some interesting changes are:

• Update pull to handle of non-https urls in descriptors
• Install apparmor parser for arm64 and update seccomp to 2.5.1
• Add support for clone3 syscall to fix issue with certain images when seccomp is enabled
• Add image config labels in CRI container creation
  For the complete list of changes please refer to the upstream release page 2.

runc
It was updated to version 1.1.0. There are many improvements and bug fixes which can be found in the upstream release page. Some deprecations and removals which might impact the upgrade are presented below:

Deprecation

• runc run/start now warns if a new container cgroup is non-empty or frozen; this warning will become an error in runc 1.2
  Removals

• cgroup.GetHugePageSizes has been removed entirely, and been replaced with cgroup.HugePageSizes which is more efficient

• intelrdt.GetIntelRdtPath has been removed. Users who were using this function to get the intelrdt root should use the new intelrdt.Root instead.

Ruby 3.0

PHP now defaults to version 8.1.2

OpenLDAP 2.5.x

PostgreSQL 14

MySQL 8.0

And much more.. Discuss! Test!

enJoy!

[girish]

Anyone know which VPS provider has this already? Would be good to give cloudron install a test run there.

[robi]

@girish any that allows for custom .iso OS installs. Most won't offer betas before the official GA release.

[nebulon]

Just saw that Vultr already has that one, I will give it a spin.

[robi]

After adjusting the installer for 22.04 the first fail is at the mysql server.

=> Updating apt and installing script dependencies
=> Checking version
=> Downloading Cloudron version 7.1.4 ...
=> Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details

Perhaps fix the fail message to be on a new line. I changed the echo line to this:
printf "\nInit script failed. See ${LOG_FILE} for details\n\n"

$ tail -f /var/log/cloudron-setup.log

Package mysql-server-5.7 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  mariadb-test mariadb-server-10.6

E: Package 'mysql-server-5.7' has no installation candidate

[girish]

The init script will have to be adjusted in various places.

mysql_package=$([[ "${ubuntu_version}" == "20.04" ]] && echo "mysql-server-8.0" || echo "mysql-server-5.7")

[robi]

@girish mysql-server-8.0 is available in 22.04

# apt info mysql-server

Version: 8.0.28-0ubuntu4
Priority: optional
Section: database
Source: mysql-8.0
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
...

[mehdi]

About this, @girish is there a good reason why the MySQL and other services used by Box are not themselves containerized ? It would probably make ubuntu version updates significantly easier

[girish]

@mehdi MySQL should probably be containerized and would have helped here (in fact, the npm test uses mysql in a docker container since @nebulon and I develop with different distros).

For box code, we attempted this long time ago. From what I remember, it was tricky to containerize the backup code. I think the basic issue was that the backup code somehow needs to access the fs mounts of existing containers and future app containers to do a backup.

[robi]

@girish said in Ubuntu 22.04 LTS (Jammy Jellyfish) Beta:

For box code, we attempted this long time ago. From what I remember, it was tricky to containerize the backup code. I think the basic issue was that the backup code somehow needs to access the fs mounts of existing containers and future app containers to do a backup.

That sounds more like a docker/runc problem.

• Take another look at Sysbox from Nestybox.com (think runc-ng) which has better interfaces and isolation.

• Colima seems to solve some of these issues in a way.

• OpenEBS for localPV from mayadata.io

[RoboMod]

@girish @nebulon, when do you expect 22.04 LTS to be officially supported by Cloudron? I'm planning to move to a fresh installation when possible.

[nebulon]

@RoboMod given that there is plenty of LTS time left on 20.04 I don't think we are in a rush to support it very soon. For a start I guess it makes to just wait a bit anyways for upstream to iron out any first hit issues.

This also is related to binary releases of other components like docker, nginx, ... which we download explicitly from their repos instead of the Ubuntu ones.

Then further the VPS provider often provider their own slightly changed Ubuntu variants, so also here I think it makes sense to wait a bit for them to settle.

Of course, if there is a security issue or such, which requires us to act faster, then the situation changes.

[RoboMod]

@nebulon Thanks for the explanation! So, moving to 20.04 LTS first and upgrading later sounds reasonable.

[girish]

Since this got released today, I tried to install Cloudron. Mostly everything works but nginx packages are not there yet - http://nginx.org/packages/ubuntu/pool/nginx/n/nginx/ . So, we have to wait till they provide the packages for ubuntu 22.04 (I tried older packages but they don't work because ubuntu 22 seems to use libssl3 instead of libssl1.1).

[robi]

@girish DB issue was resolved?

[girish]

@robi yes, just had to select the right package in ubuntu 22.04 . Just https://git.cloudron.io/cloudron/box/-/commit/f5a2e8545b5e7e5c1d17a18790fccff0a5ea7669 was needed.

[robi]

@girish sweet, thanks for the link.. it's clearer how all the changes in the front end script are also reflected in the backend init script.

I'll try the new installer again,

Thanks!

[LoudLemur]

@robi
If you are trying 22.04 Jammy Jellyfish in a Virtual Machine, there can be issues with Wayland during login. (Scroll to 4:00 here:
https://odysee.com/@DistroTube:2/is-ubuntu-22.04-the-best-ubuntu-in-years:f
Mouse over to the bottom right and activate the dropdown menu there.
Wayland isn't famous for playing well with proprietary nvidia drivers.
If you want a leaner experience and Lubuntu, then there is a LxQt 1.1 PPA here:
https://launchpad.net/~severusseptimius/+archive/ubuntu/lxqt

[LoudLemur]

@nebulon KDE neon usually waits till the x.04.1 release before proceeding with a major update. There is usually a load of people looking at a new LTS release, and tons of useful feedback.

[robi]

@LoudLemur Slow your roll. There is no Wayland in a server install.