@parcel/rust v2.13.0 now appears to require GLIBC_2.29

[paulbrimicombe]

🐛 bug report

• With @parcel/rust v2.12.0 parcel runs fine on an OS that uses GLIBC_2.28 (e.g. Rocky Linux 8)

• With @parcel/rust v2.13.0 parcel fails with the following error:

  Error: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /<SNIP>/node_modules/@parcel/rust/parcel-node-bindings.linux-x64-gnu.node)

🎛 Configuration (.babelrc, package.json, cli command)

No babel or other special configuration required

🤔 Expected Behavior

Within a major semver version, parcel should continue to run in a given environment (GLIBC_2.28).

😯 Current Behavior

Parcel fails with a GLIBC version error on environments that use GLIBC_2.28

🔦 Context

We are unable to run parcel on our build environment

💻 Code Sample

Steps to reproduce:

• Start a Docker container that uses GLIBC_2.28: docker run -it rockylinux:8 /bin/bash
• Enable Node 18: dnf module -y enable nodejs:18
• Install Node 18: dnf install -y nodejs
• Navigate to a temporary directory: cd /tmp
• Initialise an NPM package: npm init -y
• Install parcel: npm install parcel
• Run parcel: node_modules/.bin/parcel
  • This will error with Error: /lib64/libm.so.6: version GLIBC_2.29' not found`
• Forcibly downgrade @parcel/rust by adding: "overrides": { "@parcel/rust": "2.12.0" } to the package.json file
• Run npm install
• Run parcel: node_modules/.bin/parcel
  • No errors related to GLIBC versions

🌍 Your Environment

Software	Version(s)
Parcel	2.13.2
Node	18
npm/Yarn	9
Operating System	Rocky Linux 8

[devongovett]

Probably due to #9849 and #9841. I believe the CentOS image we used to compile on no longer builds (CentOS is defunct). It is getting much harder to support these super old versions...

[paulbrimicombe]

It is getting much harder to support these super old versions...

While I agree that supporting a variety of OS versions is tricky, it's probably worth noting that Rocky 8 (a very widely used CentOS replacement / equivalent) is still in security support for another 4.5 years.

If you'd like any help replacing your CentOS image with some other RedHat Enterprise Linux 8 equivalent then do let me know.

[zacharytyhacz]

Getting same issue on Debian GNU/Linux 10 (buster) x86_64

[BorisAnthony]

Vercel is suddenly giving me this error when I deploy a project to it…
and my requirements call for "parcel": "^2.7.0"

Full error:

Error: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /vercel/path0/node_modules/@parcel/rust/parcel-node-bindings.linux-x64-gnu.node)
    at Module._extensions..node (node:internal/modules/cjs/loader:1460:18)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:177:18)
    at Object.<anonymous> (/vercel/path0/node_modules/@parcel/rust/index.js:188:31)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12) {
  code: 'ERR_DLOPEN_FAILED'
}
ERROR: "prod:parcel" exited with 1.
Error: Command "npm run build" exited with 1

[sseidel16]

Our project is now having issues as well, and we have to use newer parcel because the parcel library bundler requires a newer version of parcel, so we are stuck.

[calvinl]

Any movement or plans to try and resolve this? It can be quite difficult for some people to get their companies to upgrade base OSes.

[devongovett]

I'd like to, we just need to find a docker image with an older glibc that we can build on

[calvinl]

@devongovett Happy to assist with that, what other requirements would the docker image need?

[devongovett]

it needs to be basically the same as the official Nodejs images but on an OS that uses an older glibc. I'm not sure if any of these already do that, or if we need to create a new one with a different distro. https://github.com/nodejs/docker-node/tree/main/22

[calvinl]

It looks like Debian 10 (Buster) uses glibc 2.28. Buster isn't available in any of the official Node images though. I would imagine we'd have to update the github action to build from a Dockerfile with debian:buster as the base, then install Node 22 on it. Is Node22 a requirement?

[mischnic]

An alternative solution would be https://github.com/corsix/polyfill-glibc