MongoDB and kernel 6.19 · Your answer
Still exits. Sorry.
Thank you for telling us. Here is what to check next, what the guide does not cover, and how to tell us what you ran.
We count visits to this page from our ordinary web logs, as we do for every page. There is no form, no script and no cookie.
Check these first
- Make sure the variable reaches mongod. It has to be in the container's environment:
env:under the service container,-ewithdocker run, orenvironment:with Compose. Release 1.12.1 ofsupercharge/cannot pass it.mongodb-github-action - Check which kernel the job runs on. On Fedora, Arch or an unfixed Ubuntu the kernel itself may lack the fix; see Other kernels.
- On kernel 7.1 or later, 8.0.21–8.0.29 and 8.3.0–8.3.8 still exit: they block every kernel from 6.19 on. Move to a newer patch release.
What the guide does not cover
- We did not run the service-container YAML on GitHub Actions, or run
supercharge/.mongodb-github-action - We did not run MongoDB 7.0.
- We did not measure the speed cost of rseq=1, or test crashes on an unfixed kernel.
How we tested is in the guide.
Tell us what you ran
Email the image tag, the runner label and the first error line. We read each one.
Send versions and error lines only, not passwords, tokens, connection strings, customer data or private links. See our Privacy page.