Problem with python slim base docker image in aws fargate

[lucas-wa]

I spent many days debugging a container that I deployed to AWS Fargate because the corresponding service in the cluster was marked as healthy, but the task was marked as unhealthy, even though the server was correctly responding to calls to the /healthy route. After changing the Docker image to use version 3.10.14 of Python instead of python-slim, the task was marked as healthy. My theory is that the base version might have limitations in threading, processing, or optimizations and was slow to respond to requests, but I didn't find anything that satisfactorily explains this.