question: Running lambda in CI using REMOTE_DOCKER=true #4801
Labels
area: ci
Running LocalStack in CI environments
type: question
Please ask questions on discuss.localstack.cloud
Is there an existing issue for this?
Question
I have stared at this problem too long, I was wanting to see if anybody else has this scenario.
We have a setup that uses lambdas along with a bunch of other things. Our CI pipeline runs some integration tests which rely on those lambdas to processes some SQS messages.
Initially we were running in local mode where we can map the code into the container that executes the lambda. Useful for development albeit really slow. The local mode does not appear to work when using docker-reuse for the lambda execution.
Locally I can get the setup working using docker-reuse executor mode, where the packages are pulled from S3. Starting up localstack in CircleCI there seems to be an issue with configuring the lambda functions.
Any call to
awslocal lambda
, for exampleawslocal lambda list-functions
causes a 500 error. All the other commands work.The error from localstack is that it is getting a connection refused from
localstack:4566
. If I connect to the CircleCI over ssh and poke around, localstack is running and I can executecurl http://localstack:4566/2015-03-31/functions/
and get a response. But runningawslocal lambda list-functions
returns a 500.I have tried configuring all sorts of environment variables mentioned in the docs that relate to hostnames and networks
This is the stack from the localstack logs:
Anything else?
No response
The text was updated successfully, but these errors were encountered: