# Kernel version upgrade required when manually updating discourse

**URL:** <https://meta.discourse.org/t/kernel-version-upgrade-required-when-manually-updating-discourse/253756>\
**Category:** Self-hosting\
**Created:** [February 1, 2023, 9:16pm UTC](https://meta.discourse.org/t/kernel-version-upgrade-required-when-manually-updating-discourse/253756 "2023-02-01T21:16:26Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [March 24, 2023, 9:37am UTC](https://meta.discourse.org/t/kernel-version-upgrade-required-when-manually-updating-discourse/253756/27 "2023-03-24T09:37:32Z")

</div>

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](https://github.com/discourse/discourse_docker/pull/673) 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:

```plaintext
  # 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.)

---

_[View the full topic](https://meta.discourse.org/t/kernel-version-upgrade-required-when-manually-updating-discourse/253756)._