/lib64/libc.so.6:找不到版本"GLIBC_2.32"

问题描述

我将通过基本示例在Ubuntu上构建lambda.它的构建没有任何错误，但是如果我在崩溃时使用以下命令在AWS上载并对其进行测试:

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"
}

日志输出为:

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

推荐答案

FWIW，在Quarkus中，我们有一个称为容器内构建的功能，该功能允许在与运行时图像兼容的容器内创建本机图像.使用.

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.

使用 -Dquarkus.native.container-build = true 可以实现.

并不是说您应该迁移到Quarkus，但是如果您要构建本机映像，则确实需要在与运行时环境兼容的环境中构建它们，这样最终将不得不在容器中进行构建.

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.

这篇关于/lib64/libc.so.6:找不到版本"GLIBC_2.32"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！