mik-laj opened a new pull request #16180:
URL: https://github.com/apache/airflow/pull/16180


   We had a race condition when the containers were started. All `airflow-*` 
containers were started simultaneously, but airflow-worker, airflow-scheduler 
and airflow-webserver require the database to be initialized first. This was 
sometimes done before the containers were started, but sometimes the container 
referred to a table that was not migrated.  Now the database is always 
initialized before the rest of the containers are started.
   
   Example: 
https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1621711385211600
   CC: @marclamberti
   PS.  I working on examples for other configuration: 
https://github.com/mik-laj/airflow-docker-compose-examples
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.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.

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


Reply via email to