Skip to content
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

Workarounds docker-compose-v2 environment passing #17052

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jul 16, 2021

The docker-compose v2 parsing of env file bug detected
in #16949 and eventual disabling of docker-compose-v2 in #16989
found another workaround after discussing with docker-compose
maintainers in docker-archive/compose-cli#1917

The VAR=${VAR} pattern seems to work for all cases for Airflow
because we never rely on the fact if variable is set or not -
we always take into account value of the variable (that is by
design and strictly followed everywhere). Therefore we are
sure this workaround is going to work for us.

However we should remove that workaround once the bug is fixed in
Docker-Compose V2.


^ 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.

The docker-compose v2 parsing of env file bug detected
in apache#16949 and eventual disabling of docker-compose-v2 in apache#16989
found another workaround after discussing with docker-compose
maintainers in docker-archive/compose-cli#1917

The VAR=${VAR} pattern seems to work for all cases for Airflow
because we never rely on the fact if variable is set or not -
we always take into account value of the variable (that is by
design and strictly followed everywhere). Therefore we are
sure this workaround is going to work for us.

However we should remove that workaround once the bug is fixed in
Docker-Compose V2.
@potiuk
Copy link
Member Author

potiuk commented Jul 16, 2021

@oyarushe - so it turned out to be more complex but we seem to have a temporary workaround that seems to works for both docker and docker-compose (see docker-archive/compose-cli#1917)

@potiuk potiuk requested a review from ephraimbuddy July 16, 2021 14:58
@oyarushe
Copy link
Contributor

@oyarushe - so it turned out to be more complex but we seem to have a temporary workaround that seems to works for both docker and docker-compose (see docker/compose-cli#1917)

yeah, I monitored all things regarding it. Nice work @potiuk!
and thanks for fixing my fix :)

@potiuk
Copy link
Member Author

potiuk commented Jul 16, 2021

ACH And found a problem there with PACKAGE_FORMAT variable :)

@potiuk
Copy link
Member Author

potiuk commented Jul 18, 2021

closing as this does not really work for docker.

@potiuk potiuk closed this Jul 18, 2021
@potiuk potiuk deleted the fix-breeze-for-docker-compose-2-with-workaround branch July 29, 2022 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants