run on newer Linux kernels

[MarDiehl]

error message is:
MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB. See https://jira.mongodb.org/browse/SERVER-121912 for more information.

according to OpenCode, 8.0.4 is working in all cases. I can confirm that for 7.1.5-arch1-2

[DanielYang59]

Hi @MarDiehl ,

As far as I know containers would use the host linux kernel so changing the image version here wouldn't result in the containers "run on newer Linux kernels"

I have been personally using this workaround for dev (#245 (comment)) but I'm not sure if this is suitable for non-testing env, as MongoDB 8.0 prior to 8.0.5 has CVEs:

Due to CVE-2025-6709, in MongoDB 8.0 prior to 8.0.5, MongoDB Server is susceptible to a denial of service vulnerability due to improper handling of specific date values in JSON input when using OIDC authentication. This can be reproduced using the mongo shell to send a malicious JSON payload leading to an invariant failure and server crash.

Due to CVE-2025-6710, in MongoDB 8.0 prior to 8.0.5, MongoDB Server may be susceptible to stack overflow due to JSON parsing mechanism, where specifically crafted JSON inputs may induce unwarranted levels of recursion, resulting in excessive stack space consumption. Such inputs can lead to a stack overflow that causes the server to crash which could occur pre-authorisation.

The this TCMalloc incompatibility guard was added in 8.0.21:

• https://github.com/mongodb/mongo/blob/08e0c4612b855c4e73385c2ec838588f82d8a19b/src/mongo/db/startup_check_rseq.cpp#L97-L107

Previous way to patch was to disable glibc RSEQ for this container with a potential performance loss, i.e.:

  mongo:
    environment:
      GLIBC_TUNABLES: glibc.pthread.rseq=1

And upon a second look this incompatiblity has been solved from the Linux kernel side:

Linux kernel version 7.0.14 and later resolves this incompatibility. To run MongoDB on an affected system, upgrade to Linux kernel version 7.0.14 or later.

And your kernel (7.1.5-arch1-2) should have already carried this fix.

[blueraft]

There's another reason why were not able to bump this version yet.

We upgraded from mongo 5 -> mongo 8 earlier this year. For the automatic upgrade to work, we needed to have the final version set to 8.0.