-
Notifications
You must be signed in to change notification settings - Fork 42
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
segmentation fault (core dumped) #57
Comments
FYI after trying many different configurations the only way I could get this to work was as a Lambda container image. Here's the Dockerfile I used for reference:
Then you have push the image to an ECR repository and create the lambda function with:
|
That's annoying!
I don't have a solution but surely it's just a question of installing the pip packages using the correct docker image. Did you try using
|
That image doesn't have the necessary toolchain.
|
What if you run the
|
Hi, I followed the instructions under
Running Locust on AWS Lambda
but all I get is this error when I runinvokr.py
:Any pointers what I might be doing wrong? I'm building the Lambda package on MacOS Big Sur using these commands:
The text was updated successfully, but these errors were encountered: