Ubuntu 22.04 LTS (Jammy Jellyfish) Beta
-
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
-
-
@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.
-
@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 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.
-
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
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 -
I managed to mostly getting it working. Some interesting changes:
- cgroup v2 is enabled by default - https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
- Private home directories by default - https://discourse.ubuntu.com/t/private-home-directories-for-ubuntu-21-04-onwards/
- nginx upstream has not offered jammy binaries yet, so we have reverted to using ubuntu packages for nginx. On ubuntu 18 alone, we continue to use upstream packages for TLS v1.3
- Python 3 default