Pages build failed when using Node 18.12.1 due to missing GLIBC

Any updates on when Pages build failed when using Node 18 due to missing GLIBC will be resolved? Node 18 is now the LTS and I’m still seeing this as well.

10:46:25.328	Success: Finished cloning repository files
10:46:26.069	Installing dependencies
10:46:26.081	Python version set to 2.7
10:46:28.127	Attempting node version '18.12.1' from .nvmrc
10:46:29.593	Downloading and installing node v18.12.1...
10:46:30.060	Downloading https://nodejs.org/dist/v18.12.1/node-v18.12.1-linux-x64.tar.xz...
10:46:30.623	Computing checksum with sha256sum
10:46:30.761	Checksums matched!
10:46:34.977	node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
10:46:34.977	node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
10:46:34.977	node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
10:46:35.033	nvm is not compatible with the npm config "prefix" option: currently set to ""
10:46:35.036	Run `npm config delete prefix` or `nvm use --delete-prefix v18.12.1` to unset it.
10:46:35.036	Failed to install node version '18.12.1'
10:46:35.041	Failed: build command exited with code: 1
10:46:35.950	Failed: an internal error occurred
1 Like

Unfortunately Node.js 18 is unsupported at this time, but will be supported in the upcoming Pages Build Image v2. For more information see the following discussion:

1 Like

Thanks! I assumed it was coming but didn’t know where to look to keep up with it.

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