We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
First off, thanks!! This is super cool.
I am a heavy user of SAM for nodejs apis and other Lambda's triggered by S3 uploads.
I am trying to get this to work and am getting the same error both locally with sam local invoke, and when deployed to AWS.
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
I am trying to use nodejs 14 , not sure if that would be an issue.
Any thoughts?
The text was updated successfully, but these errors were encountered:
Hi @digidigo
wondering if you got any work arounds on this ? I am experiencing a similar issue.
Sorry, something went wrong.
No branches or pull requests
First off, thanks!! This is super cool.
I am a heavy user of SAM for nodejs apis and other Lambda's triggered by S3 uploads.
I am trying to get this to work and am getting the same error both locally with sam local invoke, and when deployed to AWS.
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
I am trying to use nodejs 14 , not sure if that would be an issue.
Any thoughts?
The text was updated successfully, but these errors were encountered: