-
Notifications
You must be signed in to change notification settings - Fork 475
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
Workaround: .NET Custom Runtime fails with ARM #920
Comments
Even better would be with a conditional item group:
Otherwise the application won't be runnable on other platforms, e.g. on a developer machine or any non-linux-arm64 system. |
I'm trying to update our lambda project to NET Core 7. I'm including Microsoft.ICU.ICU4C.Runtime, but I'm getting the following error. Failed to load /var/task/libcoreclr.so, error: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /var/task/libcoreclr.so) |
See #1310 |
Closing the issue since the related issue #1310 is now closed. |
|
#.NET Custom Runtime issues with libicu
Custom runtimes are typically used to run newer versions of .NET then supported in the Lambda Managed runtimes. When deploying a .NET Lambda function using Custom Runtimes, the function may fail due to issues with the
libicu
library. This problem manifests differently depending on the Amazon Linux version and architecture:On Amazon Linux 2 with ARM64 architecture:
The function fails with the following error:
This is due to .NET requiring version 53 and above of the native dependency
libicu
and Amazon Linux 2 has version 50. We are looking at getting the version of libicu updated in Amazon Linux 2.On Amazon Linux 2023 (all architectures):
The function fails because libicu is not present on the system at all. https://docs.aws.amazon.com/linux/al2023/ug/amzn2-al2023-ami.html
To workaround this issue, you can include a newer version of libicu in your Lambda function that will unblock custom runtimes. To include libicu with your .NET Lambda function, include the following snippet in your csproj or fsproj file.
The text was updated successfully, but these errors were encountered: