SQS does not come up reliably

Platform
,
1

we are looking at using localstack to provide a mock SQS and S3 for our unit tests. We aren’t having any issue with S3, but we are finding SQS does not always come up reliably.

the docker command to start is simple enough:
docker create -e AWS_DEFAULT_REGION=us-east-1 -e EDGE_PORT=4566 --publish-all localstack/localstack:latest
(then use docker run and docker inspect to find the locally assigned port)

followed by a CreateQueue api request. We are finding this often, but not always, fails with
operation error SQS: CreateQueue, exceeded maximum number of attempts, 20, https response error StatusCode: 0, RequestID: , request send failed, Post "http://localhost:32929/": EOF"

(specific port number is variable, of course)

S3 operations are not having any issue.

Troubleshooting is made even harder by the fact this doesn’t fail locally on our arm64 machines, the failure is only happening when run as a github action.

1 Like
2

update: we tracked this to the test code launcher not properly passing “-e EDGE_PORT=4566” (and as it is now doing so, I can now see the deprecation warning) so successive tests were not properly locating the proper instance.

1 Like
3

Hi @PaulF,

I would recommend using the start-up configuration we mentioned in our documentation, if it works as expected, then start making changes.
Get Started documentation: Installation | Docs (localstack.cloud)

Please have a look at our docker-compose.yml template for the basics and our Configuration | Docs (localstack.cloud) for all the other configuration options.