Install error: `'GLIBC_2.33' not found`

[chgeo]

With latest 11.9.0, I get this error:
10:04:52 INFO - npm error prebuild-install warn install /lib64/libc.so.6: version 'GLIBC_2.33' not found (required by .../node_modules/better-sqlite3/build/Release/better_sqlite3.node)

This happens on an older SLES image that worked just fine with the previous version of better-sqlite3.

I guess the change of the GLIBC baseline version was done by mistake, maybe done in #1341.

[chgeo]

Similar issues from the past: #990, #403

[m4heshd]

This is one of the challenges we predicted in #1341. Unfortunately, we hardly have any alternatives other than going with a custom runner.

[chgeo]

Have you checked on the options mentioned in #990 for decoupling the runner image from GLIBC (like using an older node base image)?

For the release process, I would expect a conscious decision on such a bump of the GLIBC baseline version. The 11.9 release notes do not mention this as a breaking change.

[m4heshd]

We already use the node:18-bullseye image for the arm builds. Can't remember exactly why we didn't go that route. Tests were done a long time ago.
As I've mentioned in #990 (comment) I tested this extensively and there were practical issues but just can't remember what those were exactly.

Anyways, @mceachen should chime in for this. He might remember or give you a good reason for why we try to keep build automation stuff as current as possible. For me, it's the constant need for maintenance and unintended outcomes. Might not apply to this very case, but that's something I'm accustomed to.

Although, in this case, I think we're okay with the node:18-bullseye container for now since the later node versions are good with glibc >= 2.28. What do you think @mceachen?

[chgeo]

Any update here @mceachen ?

[mceachen]

Indeed--I didn't think through the impact of the build runner upgrade. Derp.

I'm fine with running the builds in bullseye, and I think it's better to have the x64 and arm builds run in as similar a way as possible, if nothing more than to avoid possible inadvertent discrepancies between distros and build tooling.

@chgeo or @m4heshd if you can, please submit a PR to update the build.yml, I'll review it as soon as I can. (I can't self-approve PRs on this repo)

[m4heshd]

@mceachen This should get it done.

[chgeo]

Thanks. I can confirm that 11.9.1 works.