-
Notifications
You must be signed in to change notification settings - Fork 293
When using slim, .so files are being broken #318
New issue
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
Comments
Same here. I'm using {
"errorMessage": "Unable to import module 'handler': /opt/python/cv2/cv2.cpython-37m-x86_64-linux-gnu.so: ELF load command address/offset not properly aligned",
"errorType": "Runtime.ImportModuleError"
} This is my pythonRequirements:
dockerizePip: non-linux
slim: true
zip: true
layer:
name: ${self:service}-python-requirements
description: Python requirements lambda layer
compatibleRuntimes:
- python3.7
licenseInfo: GPLv3
allowedAccounts:
- '*' The error persists even using the flag
|
I'm seeing the same issue when adding Pillow as a dependency. Setting |
I'm seeing the same issue as well with |
After reading this issue, I realized that my |
Could we get a new release that includes this fix, please? |
I had this problem persist through trying both The error occurred after adding the Error:
What fixed it for me was to set |
Harumf I'm having the same problem but sadly still no luck. Interestingly I don't see a Seems to me a binary incompatibility issue. |
A note for anyone running into this error: It may not have to do with your serverless packaging at all. I spent a bunch of time figuring out our error and it was related to a version incompatibility between numpy 1.8.0 and scipy 1.5.4. The error showed as: When I downgraded scipy to 1.4.1, the problem was solved. |
Issue was mentioned on thread for another issue - #216 (comment)
Trying to deploy python lambda app using circleci. Build and deploy is successful but then when lambda runs we get the following error
Plugin configuration:
Same serverless.yml configuration works when I run it from my own mac OS computer.
On circleci I've tried using
dockerizePip: true
with thecircleci/classic:201808-01
machine and usingdockerizePip: non-linux
using thecircleci/python:3.7-node
docker image. In the latter case the whole build takes place in the circleci docker container - originally I thought this was the cause of the issue.I don't think I can stop using slim because the file not meet the aws lambda requirements.
The text was updated successfully, but these errors were encountered: