-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GLIBC_2.28 not found #874
Comments
I believe you will need to move to Amazon Linux 2023 as AL2 doesn’t support newer GLIBC versions. That was my experience when I was using AL2. |
That's correct. Deploy your function with the runtime |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Thanks y'all, it worked! 😃 |
We are deploying to aws-cn so Amazon Linux 2023 is unfortunately not yet an option for us. Our solution is to add {
bundling: {
cargoLambdaFlags: ['--target', 'aarch64-unknown-linux-gnu.2.26'],
},
runtime: 'provided.al2'
} to the |
Thanks for solving, AWS gov-cloud won't be getting AL2023 for lambda for the foreseeable future so this is a big help. |
@tbar4 The Lambda AL2023 runtimes are now available in China regions: https://www.amazonaws.cn/en/new/2024/amazon-lambda-adds-support-for-amazon-linux-2023-runtimes-in-amazon-web-services-china-regions/ |
This helps to fix the failures I was getting about missing GLIBC_2.28 which is no longer available on al2 Reference: awslabs/aws-lambda-rust-runtime#874
Since I upgraded to Rust 1.78, I am facing the following issue while deploying lambda functions:
I checked older issues and found somehow similar ones, but it looks like I am building and deploying my functions correctly though:
My runtime is Amazon Linux 2:
The functions are built with
cargo lambda build --release
My rust version is:
And I am using
lambda_runtime = "0.11.1"
.Could it be that Rust 1.78 cannot yet run on Amazon Linux 2 runtimes?
The text was updated successfully, but these errors were encountered: