Currently, we copy all dynamic libraries from dependencies into the final deployment image. This is not optimal - AWS Lambda deployment script uses ldd to recursively find only those shared libraries, that are actually used by the binary. We could apply the same to optimize container size.
The same happens for code packages - we don't need to pack and deploy system libraries, which we know will be available on Lambda; we should only pack our dependencies from /opt/.
For arm64 (#265), we can use an ldd replacement.
Currently, we copy all dynamic libraries from dependencies into the final deployment image. This is not optimal - AWS Lambda deployment script uses
lddto recursively find only those shared libraries, that are actually used by the binary. We could apply the same to optimize container size.The same happens for code packages - we don't need to pack and deploy system libraries, which we know will be available on Lambda; we should only pack our dependencies from
/opt/.For arm64 (#265), we can use an ldd replacement.