How to solve this Glibc 2.22 version not found on amazon Lambda

The OS Lambda uses for it's containers is essentially a recent Amazon linux. If a library was built on a different platform, it can get linking errors like that. Try rebuilding that package and any other compiled parts of your lambda on an Amazon Linux box.

I tried to compile the zip on amazon ec2 server.
then when i run on lambda i get this error .
libffi-d77877bc.so.6.0.4: cannot open shared object file: No such file or directory

Edited by: Adithya on Oct 5, 2017 1:32 AM

Edited by: Adithya on Oct 5, 2017 1:33 AM

Then your build becomes more complicated. You have a dependency on libffi, which means you needed to install it to compile your dependencies. However, you'll also need that library to run your packages, which means you need to bundle it with your package, as It wasn't installed by default, and lambda runs a default Amazon Linux image. This will occur for all dependencies that you needed to install during compilation.

Thanks i will try and get back to you