potiuk opened a new pull request #16959:
URL: https://github.com/apache/airflow/pull/16959


   The #16950 aimed to fix an incompatibility introduced by
   beta version of docker-compose v2 (which is automatically pushed
   to MacOS users now).
   
   The issue is documented in
   https://github.com/docker/compose-cli/issues/1917
   
   Unfortunately it has an undesired side-effect that the same file
   cannot be used to specify list of variables for docker command
   (the variables come empty).
   
   Until the problem is solved, we need to keep two copies of those
   variable files. Not ideal, but hopefully the issue will be solved
   soon and we can go back to original env file in docker-compose v2.
   
   <!--
   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/main/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/main/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.

To unsubscribe, e-mail: [email protected]

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


Reply via email to