Pages build failed when using Node 18 due to missing GLIBC

14:50:03.325 Initializing build environment. This may take up to a few minutes to complete
14:50:05.529 Success: Finished initializing build environment
14:50:05.529 Cloning repository…
14:50:17.816 Success: Finished cloning repository files
14:50:18.070 Installing dependencies
14:50:18.082 Python version set to 2.7
14:50:20.366 Attempting node version ‘18.0.0’ from .node-version
14:50:22.091 Downloading and installing node v18.0.0…
14:50:22.595 Downloading
14:50:23.024 Computing checksum with sha256sum
14:50:23.165 Checksums matched!
14:50:27.582 node: /lib/x86_64-linux-gnu/ version `GLIBC_2.27’ not found (required by node)
14:50:27.582 node: /lib/x86_64-linux-gnu/ version `GLIBC_2.25’ not found (required by node)
14:50:27.583 node: /lib/x86_64-linux-gnu/ version `GLIBC_2.28’ not found (required by node)
14:50:27.658 nvm is not compatible with the npm config prefix option: currently set to
14:50:27.660 Run npm config delete prefix or nvm use --delete-prefix v18.0.0 to unset it.
14:50:27.665 Failed to install node version ‘18.0.0’
14:50:27.670 Failed: build command exited with code: 1


Yes we are aware of this issue and I hope to have it resolved soonish. No timeline though on that. For now, I’d suggest using NodeJS 17


Thanks for your quick reply! Would appreciate it if the issue could be fixed ASAP, as Node 18 now officially supports the fetch API with a stable implementation.


Yep we will get it fixed ASAP. For reference, Fetch was also backported to NodeJS 16 yesterday so you can use that for now: node/ at master · nodejs/node · GitHub


This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.