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

Do not set undefined inherited variables #218

Merged
merged 1 commit into from Feb 17, 2022

Conversation

kcboschert
Copy link
Contributor

Prior to Docker-Compose v2, inherited variables that were undefined on the host would not be defined in the container. This returns the original behavior.

This resolves docker/compose#9031

…the provided lookup function. This restores the original behavior prior to docker-compose v2.

Signed-off-by: kcboschert <kcboschert@gmail.com>
@flemay
Copy link

flemay commented Jan 15, 2022

I just noticed your PR today. I created a PR with the same fix last year and replicated it in this repo.

At first, I thought the problem happened only when there were multiple variables in a .env file, therefore my PR was around that. Then I tried today with a single variable in .env file and the result confirmed the issue was still there.

Your PR is more accurate!

@ulyssessouza ulyssessouza merged commit be12d6c into compose-spec:master Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent Passthrough Environment Variable behavior: environment vs env_file
3 participants