When running the update per here: Manually update Discourse and Docker image to latest I get the following errors: “Kernel version 4.4.0-210-generic not supported, please upgrade to at least 4.14.0” What do I need to do here? I can’t find support topics on upgrading the kernel version.

[image] Stephen: Have you considered just creating a new server on a more recent release and restoring a backup? I personally haven’t (unsure about @AMK ) - only because it would take me longer to do everything that’d be required than it would to type a single update command in to the console…

I actually haven’t tried creating a new server. Like @Richie the only thing I have installed on the server is Discourse. And exactly, I would rather run a command to get the updates than having to do complete move to a new server. I also checked my install version and looks like my site’s at versi…

@AMK (and anyone else interested!) I powered down my Digital Ocean droplet and took a full snapshot (which took around 30mins). I then ran do-release-upgrade and went from Ubuntu “16.04.7 LTS” to “18.04.6 LTS” After the reboot, I checked Discourse - all ok. I then did another release upgrade to…

That’s why I suggested: [image] Jay Pfaffman: I would spin up a new droplet and start fresh. It may be “harder” but you can do it with near zero down time (and zero downtime if you create the new one in the same data center as the old one and use a static IP), and if something goes wrong, yo…

If you rsync /var/discourse between droplets in the same data center your downtime can be pretty minimal and your fallback is just a DNS reversion. The new VPS only needs docker and potentially swap.

Hi, I also get this error running Red Hat Enterprise Linux 7, running kernel 3.10.0. RHEL8 doesn’t run much newer.

Same here, 3.1.0.beta1 running fine on CentOS7 (3.10.0-1160.76.1.el7.x86_64) Obviously the distro kernels get a ton of backports. Checking the vanilla kernel version like this has been causing grief in other projects too. Is there a way to bypass this check from the command line? —UPDATE— I edite…

Is this issue going to get more light? The system requirements do not require any kernel versions and Centos 7/RHEL 7 is not in EOL yet. Docker does not require a newer kernel either. I don’t think manually bypassing the check is the proper solution in the long term. docs/INSTALL.md main …

I was about to upgrade an older forum and got the same error. Centos7 has not reached EOL yet, could you find an alternative solution for Ubuntu 14.04?

If you believe you are running the most up to date kernel from your OS supplier (with backported fixes) you might want to try bypassing the check. I know I would! This is the issue where the check was added. I believe could just remove or comment out the exit command in your ./launcher script, in…

Mise à niveau de la version du noyau requise lors de la mise à jour manuelle de Discourse

Soutien Installation

Paracelsus Avril 15, 2023, 3:54 32

Notre système exécute les éléments suivants :

CentOS Linux release 7.9.2009 (Core)
Kernel 3.10.0-1160.88.1.el7.x86_64

Change attachment size limit without rebuilding?

Sujet		Réponses	Vues
Determining whether my VPS needs any upgrades (generally) Support	20	579	Mars 10, 2025
Ubuntu 16.04 LTS kernel compatibility? Self-hosting	12	6033	Octobre 20, 2016
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	109991	Janvier 16, 2025
Please document supported distros Self-hosting	14	1451	Juin 8, 2020
Discourse update error Self-hosting	35	2297	Janvier 30, 2023

Mise à niveau de la version du noyau requise lors de la mise à jour manuelle de Discourse

Sujets connexes