This error happens when you install Node on an operating system that has a version of GLIBC that is lower than Node can support. For example, Node v18 supports GLIBC v2.7 or later. When you attempt to install Node v18.x on any Linux OS that has GLIBC v2.6 or lower, you will get such errors.
To see the version of GLIBC that your operating system has, execute the ldd command on the terminal:
Copy$ ldd --version
I can suggest three options to resolve this issue:
- Either install Node from source code. This will allow you to recompile
- Or install an older version of Node that your OS can support
- Or upgrade your Linux OS to a newer version.
Reference: Install Node from source code
Answer from Bruce Malaudzi on Stack OverflowThis error happens when you install Node on an operating system that has a version of GLIBC that is lower than Node can support. For example, Node v18 supports GLIBC v2.7 or later. When you attempt to install Node v18.x on any Linux OS that has GLIBC v2.6 or lower, you will get such errors.
To see the version of GLIBC that your operating system has, execute the ldd command on the terminal:
Copy$ ldd --version
I can suggest three options to resolve this issue:
- Either install Node from source code. This will allow you to recompile
- Or install an older version of Node that your OS can support
- Or upgrade your Linux OS to a newer version.
Reference: Install Node from source code
Observed the same error on the Linux machine of AWS.
This error will also be observed when we have installed Node JS and when we check the version. To resolve the issue we need to have greater than GLIBCv2.6. Amazon provides Linux boxes with GLIBC v2.6 and greater version than this as well. Before starting dev work use the below command to select a suitable machine
command used : ldd --version (on Amazon Linux machine) :
node.js - /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node) - Stack Overflow
RHEL 7.9 GLIBC Errors
Install error `node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)`
Error when trying to use a node project
Try installing the active LTS version instead of latest with nvm install 16 (instead of nvm install node) as per the examples.
This was tested on the docker image amazonlinux:2 and correlates to what AWS CDK supports (ref)
Update
LTS has moved on for node, however, as per @djvg's comment, note there is a limitation with amazon linux 2 on glibc, so if requiring node > 16 will need to move to newer amazon linux version, eg: https://github.com/amazonlinux/amazon-linux-2023/blob/main/Release-Notes-Amazon-Linux-2022.0.20220728.0.md
It seems like you are using v.18.0.0 which was the latest but not well-supported.
Try uninstalling that.
Copynvm uninstall 18.0.0
Install a version that is active.
Copynvm install 16.0.0
You should now be using v16 which should be well-supported.
While Cris' answer is most likely correct in that it describes the root cause, he doesn't offer a solution compatible with the asker's environment (GoDaddy shared hosting).
According to these instructions from CodePunker, the solution is to install an older version of node.js that is compatible with whatever version of libstdc++ is installed on your GoDaddy shared host.
- If you get an error during installation saying you don't have the required GLIBC version then you need to install an older (potentially unsupported) version of Node.js
- To do that, execute nvm ls-remote --lts which will show you all the long term support Node.js versions that exist in the repository. Install an older one by issuing nvm install vX.X.X and then nvm use vX.X.X
The specific version of node.js that you'll need to install will depend on how outdated your shared host is. I tested this successfully with v10.13.0, but I just jumped to the oldest release in the current branch and did not test any newer versions.
You can also call GoDaddy Support and request that they update your host or move your site to a different shared host with more up-to-date libraries.
Update your base system or compile from source (which may also require updating your base system.) No GLIBCXX_3.4.15 symbols means your libstdc++ is from 2009 or earlier.