/lib64/libc.so.6: version `GLIBC_2.32' not found

user_5901705 0
Viewed 12891

I'm building the lambda on Ubuntu with the basic example. It builds without any errors but if I upload and test it on aws in crashes with:

{
  "errorMessage": "RequestId: 7f4d0aca-125c-4032-98dd-9ff387e5252b Error: Runtime exited with error: exit status 1",
  "errorType": "Runtime.ExitError"
}

The log output is:

START
RequestId: 7f4d0aca-125c-4032-98dd-9ff387e5252b
Version: $LATEST.~.jwtauthorizeraws.jwtauthorizerawsapplication: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./~.jwtauthorizerawsapplication)
END 
RequestId: 7f4d0aca-125c-4032-98dd-9ff387e5252b
REPORT
RequestId: 7f4d0aca-125c-4032-98dd-9ff387e5252b
Duration: 56.02 ms
Billed Duration: 57 ms
Memory Size: 128 MB
Max Memory Used: 7 MB   
RequestId: 7f4d0aca-125c-4032-98dd-9ff387e5252b
Error: Runtime exited with error: exit status 1
Runtime.ExitError
graalvm-native-image spring-cloud-function aws-lambda
3 Answers

It probably means that the glibc version used to build the executable is different than the docker environment is using.

So, check the build environment "ldd --version" will reveal the glibc version.

Now, in your docker container (docker run -ti --entrypoint=/bin/bash dockerimage:tag) type the same ldd command. You'll probably see that the versions are different. So, update either the build environment to use the same version as the docker environment or vice-versa.

The best way to avoid this is to use the runtime environment to build your native executable: this way the glibc version will always match.

user_15003800

FWIW, in Quarkus, we have a feature called in-container build, which allows to create your native image inside a container that is compatible with the runtime images we use.

Using -Dquarkus.native.container-build=true makes it happen.

Not saying you should migrate to Quarkus but if you want to build native images, you really need to build them in an environment compatible with your runtime environment so you will end up having to build in a container.

user_50435850

the environment you are executing the seems doesn't provide a Glibc version in version 2.32.

This can have several problems: the version of your the Lambda env is older, or it doesn't provide an GlibC at all (which can be the case).

if you application would be pure java (without creating an native app via graal) it would run since the java app itself doesn't depend a version of GLibC, the requirment comes from the native app.

user_34077600
Related