danw-mpl

Hello, thanks for replying. Straight forward enough. Using the standard Docker Compose way of creating named networks. Example: ```yaml services: localstack: {...} networks: - localstack {...} networks: localstack: driver: bridge...

Found a workaround for my use case. To get DNS name resolution working between containers and have Localstack available from the host (for Commandeer), I added two networks to docker-compose.yml....

I'm also getting this problem with AWS SAM, not Serverless Framework. Localstack version: 0.12.17 running with Docker Compose.

This would be amazing. We wait over two minutes every time we invoke a function because the cache is wiped out. Super frustrating when trying to develop. @justinmk3 Regarding JetBrains,...

This also breaks `opentelemetry-instrument` with Gunicorn, causing the same `Waiting for thread pool to idle before forking` error. I downgraded 1.52.0 to 1.51.1 to fix the issue.

Gotcha, so a simple workaround could likely be including other admin areas? Alternatively I was going to try getting the states as polygons from OSM places. My source is `aws:latest`.

This is still ongoing sadly. The client Python logs look like `Transient error StatusCode.UNAVAILABLE encountered while exporting traces to ...`. Any ideas would be greatly appreciated!

Fair enough. I'm actually using style 'caching' to avoid redrawing the style on every pan/zoom which causes significant declutter flickering. So ignoring the caching topic, I'd still be interested in...