Type of request: This is a ...
[x] bug report
[ ] feature request
Detailed description
When running localstack on MacOS using the example docker-compose.yml, Lambda functions can take a long time to start up.
I think this is because of existing performance issues with osxfs, the file system server in Docker for Mac.
If your using LAMBDA_EXECUTOR=docker, the copying of zipped code to new lambci/lambda containers can take a very long time.
If you're using serverless-localstack, enabling mountCode solves the slow copying, but then actually requiring your code inside the lambda function can take a long time (mostly because of node_modules).
To solve this, I disabled mounting /tmp/localstack in my docker-compose.yml
volumes:
# - "${TMPDIR:-/tmp/localstack}:/tmp/localstack"
- "/var/run/docker.sock:/var/run/docker.sock"
...
Expected behavior
...
Actual behavior
...
Steps to reproduce
Command used to start LocalStack
...
Client code (AWS SDK code snippet, or sequence of "awslocal" commands)
...
Type of request: This is a ...
[x] bug report
[ ] feature request
Detailed description
When running localstack on MacOS using the example
docker-compose.yml, Lambda functions can take a long time to start up.I think this is because of existing performance issues with
osxfs, the file system server in Docker for Mac.If your using
LAMBDA_EXECUTOR=docker, the copying of zipped code to newlambci/lambdacontainers can take a very long time.If you're using
serverless-localstack, enablingmountCodesolves the slow copying, but then actually requiring your code inside the lambda function can take a long time (mostly because of node_modules).To solve this, I disabled mounting
/tmp/localstackin mydocker-compose.yml...
Expected behavior
...
Actual behavior
...
Steps to reproduce
Command used to start LocalStack
...
Client code (AWS SDK code snippet, or sequence of "awslocal" commands)
...