-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Fixed parsing issue of _docker.env file for docker-compose v2 #16950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Oh boy! |
|
🤦 for docker v2 to not handle this case. I think we should open an issue for that |
|
I tested it with docker 2 and it works there too. Thanks for that investigation and fix @oyarushe ! |
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
|
Created an issue in docker-archive/compose-cli#1917 |
|
BTW. You will need to rebase to latest main to get it works (drill operator added a dependency) |
|
I merge it anyway - no problem with the failing tests. |
The apache#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 docker-archive/compose-cli#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.
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 docker-archive/compose-cli#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.
(cherry picked from commit 83cb237)
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 docker-archive/compose-cli#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. (cherry picked from commit 72781c0)
The apache#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 docker-archive/compose-cli#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.
(cherry picked from commit 83cb237)
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 docker-archive/compose-cli#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. (cherry picked from commit 72781c0)
(cherry picked from commit 83cb237)
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 docker-archive/compose-cli#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. (cherry picked from commit 72781c0)
It relates to issue #16949. It can't parse env file without sign
=for each variable name.I have checked for versions of Docker Compose:
1.29.2andv2.0.0-beta.6.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.