AWS Lambda runtime error: version "GLIBC_2.28" not found
- Dominant language
- JavaScript
- Stars
- 102
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hoping someone can help me with this issue. I'm uploading a Serverless project to a Lambda on AWS that has a dependency on bcrypto. When it's run, it cannot find libc.so.6 with the correct version of GLIBC_2.28.
I've attempted to build my project on an EC2 instance AWS provides of Linux 2 just to make sure it wasn't my build environment that was causing the issue, and I tried it on my own Ubuntu instance with a different, newer version also, both have the same error when run in the cloud.
Are there any settings or build parameters I can pass to include whatever libraries are necessary so the binary doesn't have to look for this file? I've never had this issue till now. I was told there was a "browser" feature for this that would allow this to be run independently but I'm having trouble finding the documentation.
More specifics:
Node 14.17.3
NPM: 7.24.0
The AWS EC2 machine I'm building from is currently running: 2.26, which is even stranger.
Any help would be greatly appreciated. Thanks.
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository file or test is named. Start by reproducing the Serverless deployment with Node 14.17.3 and bcrypto on AWS Lambda, then compare the GLIBC requirements with the stated EC2 and Ubuntu build environments. Done means the Lambda binary runs without the GLIBC_2.28 error, or the required build parameters and browser feature are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100