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.

[תמונה] 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 :blush:

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 version 3.0.0.beta16. When I click on upgrade I’m directed to “You are running an old version of the Discourse image” and that’s where I’m running into the Kernel version not supported error when try to do the update.

@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 take me beyond Ubuntu 18. Not sure which version it was going to, v20 maybe? After that next reboot, my server never came back online :pensive: I then had to restore my snapshot (which took 15mins), then I went from “16.04.7 LTS” to “18.04.6 LTS” again, then I updated Discourse. Total time, 1hrs 50mins.

That’s why I suggested: [תמונה] 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, you can just switch back to the old server. [תמונה] Richie Rich: Not sure which version it was going to, v20 maybe? Probably, and you really want to be on 2022.04.

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 edited the launcher script to bypass the check - several CentOS7 installs updated without a problem.

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 To install and self-host Discourse, follow the steps below. But if you'd rather skip the setup, maintenance, and server management, our official Discourse hosting takes care of everything for you. 👉 [Learn more about Discourse hosting](https://discourse.org/pricing) # How Do I Install Discourse? > :bell: The only officially supported installs of Discourse are [Docker](https://www.docker.io/) based. You must have SSH access to a 64-bit Linux server **with Docker support**. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc. Simple 10 minute basic install: [**Beginner Docker install guide**][basic] Powerful, flexible, large / multiple server install: [**Advanced Docker install guide**][advanced] ### Why do you only officially support Docker? Hosting Rails applications is complicated. Even if you already have Postgres, Redis and Ruby installed on your server, you still need to worry about running and monitoring your Sidekiq and Rails processes, as well as configuring Nginx. With Docker, our fully optimized Discourse configuration is available to you in a simple container, along with a web-based GUI that makes upgrading to new versions of Discourse as easy as clicking a button. ### Hardware Requirements This file has been truncated. show original

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 this paragraph: # At least minimum version if compare_version "${kernel_min_version}" "${test}"; then echo "ERROR: Kernel version ${test} not supported, please upgrade to at least ${kernel_min_version}" exit 1 fi If, as a result, the upgrade still fails, then you will need to find a way to run your Discourse on a newer kernel. (It’s quite possible this advice will be felt to be off-message, but I think what’s happened is that we have a check for a version number rather than a check for a facility (urandom), and that approach can give false positives.)

שדרוג גרסת הליבה נדרש בעת עדכון ידני של discourse

תמיכה התקנה

Falco (Falco) 19 באפריל,‏ 2023,‏ 5:18pm 35

Yes, PR welcome to feature detect it properly.

נושא		תגובות	צפיות
Determining whether my VPS needs any upgrades (generally) Product Support	20	1085	10 במרץ,‏ 2025
Ubuntu 16.04 LTS kernel compatibility? Self-hosting	12	6218	20 באוקטובר,‏ 2016
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	112331	16 בינואר,‏ 2025
Please document supported distros Self-hosting	14	1586	8 ביוני,‏ 2020
Discourse update error Self-hosting	35	2725	30 בינואר,‏ 2023

שדרוג גרסת הליבה נדרש בעת עדכון ידני של discourse

נושאים קשורים