AWS Lambda runtime error: version "GLIBC_2.28" not found

[arkmoon]

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.

[arkmoon]

For anyone who happens to run into this in a google search. Finally got it working only after running the npm install in Ubuntu 18 LTS.

I'm not seeing this error anymore because it's running GLIBC 2.27 which I guess works. WOW. This was a huge headache, because even the official AWS Linux 2 image, which is supposed to be running 2.26, didn't work for some reason.

I pray this helps someone in the future, because it nearly ended me.