No LocalWorkers started when scheduler is launched in daemon mode. about airflow HOT 4 CLOSED

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

from airflow.

The documented pattern for running Airflow in Docker can be found in the Airflow guide Running Airflow in Docker. The docker compose file is a bit more extensive than the one you've shared.

Can you try following that guide? You can run everything in detached mode with docker compose up -d.

from airflow.

Thanks Ryan. I've worked around this issue by starting the scheduler last. I'm actually using AWS ECS and only made the compose file to debug the issue. I thought I would submit a bug as it did waste a couple hours of my time... and I thought it was time I try and get more involved with an open source project. Again: thanks for your help.

from airflow.

Run Airflow services in daemon it is useful only on case if there is not possible for some reason to use external daemons (e.g. systemd) or containers.

In case of containers it's best practice to separate areas of concern by using one service per container.
It is much easier to maintain and restart due to the failure, e.g. if webserver goes down you don't have to restarts scheduler and vice versa.

I'm actually using AWS ECS and only made the compose file to debug the issue.

Even if you use cloud based container service the principal pretty the same, 1 service = 1 task.

from airflow.