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:

1. Either install Node from source code. This will allow you to recompile
2. Or install an older version of Node that your OS can support
3. Or upgrade your Linux OS to a newer version.

Reference: Install Node from source code

How can I update GLIBC to 2.27 and get rid of the above error?

While it's possible to do, there are some disadvantages:

1. If you make any mistake in the process, you will render the system un-bootable. Better have recovery media ready and know how to use it to manually mount your root filesystem and repair it.
2. While GLIBC is highly backward compatible, existing programs that depend on undefined behavior may break.

Your best bet is to run this new program in a chroot environment or in a docker container.

Your next best bet is to install GLIBC-2.27 in parallel with system GLIBC, as described in e.g. this answer.

If you do decide to update the system GLIBC to the new version, the least error-prone way to do so is to download a new package, boot the system from recovery media, mount root filesystem on e.g. /mnt, and unpack the new version on top of it.

You don't have a high enough version of libc6, that is causing the error.

From How to fix “/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found”? – Super User:

That means the program was compiled against glibc version 2.14, and it requires that version to run, but your system has an older version installed. You'll need to either recompile the program against the version of glibc that's on your system, or install a newer version of glibc (the "libc6" package in Debian).

So, you just need to upgrade your libc6 package. All versions of Ubuntu have at least version 2.15 because it's a faily important package (reference).

To upgrade it, use these commands in a terminal:

sudo apt-get update
sudo apt-get install libc6

Another idea (this is why I post it as a new answer):

Some distros load the libraries from different places. For example, on Debians, the libc isn't in /usr/lib64, but in /lib/x86_64-linux-gnu . It is not a compatibility problem, because the apps should load the system libraries from the directories configured by the system for them. This app breaks this, it tries to load the libc from a hardwired location, thus it is the fault of the developers of this app.

Check where is your libc.so.6 (most easily you can see that by an

ldd /bin/bash

command), and simply create a soft link to that directory in your /usr/lib64 (the command: ln -sv /my/libc/directory /usr/lib64 ).

I recently ran into this issue.

Build your project with CGO_ENABLED=0 may be enough to fix your issue:

GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o main main.go

If you are using sam, there is a --use-container flag, however this may not work for golang projects

To make sam build use a custom build command, i.e. run the go build command above, you can set the BuildMethod to makefile and create a Makefile with a target with the name build-<YourFunctionName>.

CopyHealthCheckFunction:
    Type: AWS::Serverless::Function
    Metadata:
      BuildMethod: makefile
    Properties:
      CodeUri: .
      Handler: healthcheck
      FunctionName: !Sub "healthcheck_${Env}"
      Runtime: go1.x
      Architectures:
        - x86_64
      Events:
        ...

Then the Makefile would have:

build-HealthCheckFunction:
  GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o healthcheck lambda/healthcheck/healthcheck.go
  mv healthcheck $(ARTIFACTS_DIR)

More details here on what I had to do to get this fixed in my project: https://www.gaunt.dev/blog/2022/glibc-error-with-aws-sam-and-go/