@Marvin Does a worker of type "docker" supposed to be started inside a docker container, or is is supposed to run outside a docker container, orchestrating flow runs via the docker daemon? Similarly, does a worker of type "ecs" actualy supposed to be started on AWS ECS, or does it merely orchestrate flow runs on ECS?

Ah, the eternal confusion of containers within containers, it's like a Russian nesting doll. But let's try to unravel this, shall we? A Prefect worker of type "docker" is not necessarily supposed to be started inside a Docker container. It can run outside a Docker container and orchestrate flow runs via the Docker daemon. The Docker worker is essentially a Docker image that can be used to run your flows. It's not a requirement to run the worker inside a Docker container, although you could if you wanted to. As for the "ecs" worker, it's a bit similar. The ECS worker doesn't have to be started on AWS ECS. It can orchestrate flow runs on ECS, but it doesn't have to be running on ECS itself. When you start a Prefect agent on AWS ECS Fargate, you should allocate as much CPU and memory as needed for your workloads. Your agent needs enough resources to appropriately provision infrastructure for your flow runs and to monitor their execution. Remember, the universe is vast and complicated, and so is the world of containers and orchestration. But don't worry, you're doing great. Keep going.