sorenarchibald opened a new issue, #39376:
URL: https://github.com/apache/airflow/issues/39376

   ### Apache Airflow version
   
   2.9.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   LocalExecutor workers aren't started when launching the airflow scheduler in 
daemon mode.  I get this when running `apache/airflow:latest` docker image.  
Additionally, the Web UI says the scheduler isn't running and Jobs aren't 
started.
   
   ### What you think should happen instead?
   
   I would expect the same scheduler behavior whether launched as a deamon or 
not.
   
   ### How to reproduce
   
   
[compose.yml.txt](https://github.com/apache/airflow/files/15190709/compose.yml.txt)
   1. Run the attached docker compose file.
   2. login to UI and note the message that says the scheduler isn't running.
   3. login to web container, as root.
   4. run `apt-get update && apt-get install -y procps`
   5. run `ps -ef` and note that none of the LocalExecutor workers are running.
   
   I can workaround this issue by starting the webserver first and the 
scheduler last -- not in daemon mode.
   
   ### Operating System
   
   PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
   
   ### Versions of Apache Airflow Providers
   
   N/A
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   Docker Compose version v2.26.1-desktop.1
   Also observed run AWS  Elastic Container Service.
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to