-
Notifications
You must be signed in to change notification settings - Fork 47
Issue with libpython2.7.so.1.0 when running on nodejs v10 runtime #5
Comments
PS.: It works well with v8 |
The
However, |
Thanks @pahud |
@renatoargh Sure. Feel free to submit your PR. |
There is a PR somewhere ? Any idea to temporary solve this issue ? |
@pahud Has this issue been resolved? Is there a PR open for it? |
Hi, I will leave this issue open and any PR would be appreciated. |
Just out of curiosity, as |
We have one use case that leverages the aws s3 sync to copy the content of
a directory to an s3 bucket. Apparently manually iterating over the
directory contents and using the sdk to upload each file was too slow.
…On Sat, Dec 28, 2019 at 18:12 Pahud Hsieh ***@***.***> wrote:
Just out of curiosity, as aws-lambda-layer-awscli is originally designed
for lambda custom runtime with bash, is there any reason or scenario the
nodejs runtime will use the aws CLI rather than the aws javascript sdk?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=ABDI6ZSXAN5EROTUZNCD2SLQ27MM3A5CNFSM4IU6T7Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYT4RA#issuecomment-569458244>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDI6ZWTUL6Y34GOVCZUO7TQ27MM3ANCNFSM4IU6T7ZQ>
.
|
My use case here is exactly the same as @flesherj |
Hi, This is expected behavior for the newer Lambda runtimes which use an Amazon Linux 2 base, which include only a very minimal set of shared libraries. For the short term, you may want to try using one of the non-deprecated runtimes which use the older Amazon Linux 2018.03 base. For example, with python3.6 here is a trivial example:
However, in the long term I also recommend using your own custom runtime. |
Hi, I have the same issue. I am using this Layer https://github.com/aws-samples/aws-lambda-layer-kubectl but both use AWSCLI. Perhaps the same fix can be applied to both. I am using AWSCLI to call EKS update-config command as well as S3 sync commands. I am using Javascript for some logic. Just an FYI: https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html |
please check this new README section in the new Let me know whether it works before we merge it into master. Thanks. |
I was working on AWS CLI v2 with python3 support for Lambda And it seems to work with I am considering to start a new |
Thanks for your Edit: Ran the two |
Sounds like it works in your environemt. :-) I just ran the You can customize your Dockerfile to generate the final |
@pahud thanks for this, |
@vhadianto merged :-) |
Awesome, thank you very much :) |
Wonderful thanks! Works as expected. |
Hi @wlarch |
You can then execute I will probably write a fully explained article shortly. I found that a lot of searching and experimentation is needed to understand this examples repository. |
@wlarch |
Hi @wlarch @pahud @vhadianto I cloned the https://github.com/aws-samples/aws-lambda-layer-awscli/ and then execute
And then I did execute a lambda function in nodejs12.x version.
In result, It gives me following error.
Do you have any suggestion for me? |
Hi @logicalicy |
@Venus713 I encountered the same problem before. Did you |
@wlarch |
@Venus713 have you ensured that your Lambda function uses the layer? Check in AWS Console. |
This also happens with dotnetcore3.1. any suggestions? |
Hello,
I am getting an error with the following code:
The error is as following:
Command failed: /opt/awscli/aws --version\n/opt/awscli/bin/python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory\n
OBS: I got the layer by clicking this button:
What might have been wrong with my deployment?! Thank a lot for your work :)
The text was updated successfully, but these errors were encountered: