运行node -v命令提示`GLIBC_2.28' not found错误的解决方案咨询

Alright, let's tackle this GLIBC_2.28 not found error you're hitting when running node -v—this is super common when your system's glibc version is older than what the pre-built Node.js binary is expecting. Here are a few solid solutions you can try out:

1. Use NVM to Install a Compatible Node.js Version #

NVM (Node Version Manager) is the safest approach here because it lets you install Node.js versions compiled for older glibc releases without messing with your system's global libraries.

• First, install NVM: You can use the official installation script, or download the package from the NVM repository manually if you prefer.
• After installation, restart your terminal or run source ~/.bashrc (or source ~/.zshrc if you use Zsh) to activate NVM.
• List LTS Node.js versions that work with older glibc: Run nvm ls-remote --lts—versions like Node.js 16.x (e.g., 16.20.2) are typically compiled against glibc 2.27, which should be compatible with your system.
• Install the chosen version: nvm install 16.20.2
• Set it as your default version: nvm alias default 16.20.2
  Now run node -v again, and it should work without the glibc error.

2. Download a Statically Compiled Node.js Binary #

Statically compiled Node.js binaries include all required libraries (including glibc) within the binary itself, so they don't depend on your system's installed version.

• Find a trusted statically compiled Node.js build for your architecture (look for builds labeled "static" or check Node.js community resources).
• Download the tar.gz package and extract it to a directory of your choice, e.g.:

  tar -xzf node-v16.20.2-linux-x64-static.tar.gz -C ~/local/
  

• Add the extracted binary's bin directory to your system PATH by adding this line to your shell config file (~/.bashrc or ~/.zshrc):

  export PATH="$HOME/local/node-v16.20.2-linux-x64-static/bin:$PATH"
  

• Reload your shell config with source ~/.bashrc (or the appropriate file for your shell), then verify with node -v.

3. Compile Node.js Manually (For Advanced Users) #

If the above methods don't work, compiling Node.js directly on your system will generate a binary tailored to your installed glibc version.

• First, install the necessary build dependencies (for Debian/Ubuntu systems):

  sudo apt-get install build-essential libssl-dev python3
  

• Download the Node.js source code for a compatible version (like 16.20.2) from the official Node.js site.
• Extract the source and navigate into the directory:

  tar -xzf node-v16.20.2.tar.gz && cd node-v16.20.2
  

• Configure the build with a custom installation path:

  ./configure --prefix=$HOME/local/node
  

• Compile and install (the -j$(nproc) flag uses all your CPU cores to speed up compilation):

  make -j$(nproc) && make install
  

• Add the installation's bin directory to your PATH, then test with node -v.

Important Note: Avoid Directly Upgrading System GLIBC #

Upgrading your system's glibc directly is extremely risky—it can break other system programs that depend on the older glibc version. Only attempt this if you're confident in managing system-level library changes and have backups in place.

内容的提问来源于stack exchange，提问作者Abhay Kumar Upadhyay