Compose handles key-only .env file differently than Docker and Docker-Compose

Question

flemay opened this issue 3 years ago · comments

Hi! I have been testing docker compose with environment variables and the result differs from Docker and Docker-Compose.

Test

Define a .env file with the following:

ENV_A
ENV_B=
ENV_C=env_c

And a docker-compose.yml file:

services:
  alpine:
    image: alpine
    env_file: .env

$ docker run --rm --env-file=.env alpine env
ENV_B=
ENV_C=env_c

Here ENV_A has not been set and ENV_B is set with an empty value.

$ docker-compose run --rm alpine env
ENV_B=
ENV_C=env_c

With Docker-Compose, we get the same outcome as Docker

$ docker compose run --rm alpine env
ENV_C=env_c
ENV_A=ENV_B=

Here's where the outcome is quite unexpected: ENV_A is set with the value ENV_B=.

Compose seems to have a problem with key-only items in .env file.

Frederic Lemay · Answer 1 · Sun Nov 28 2021 09:59:03 GMT+0800 (China Standard Time)

Just realised that this issue could be in https://github.com/docker/compose? or https://github.com/compose-spec/godotenv (couldn't create an issue)?

Frederic Lemay · Answer 2 · Wed Dec 01 2021 19:36:12 GMT+0800 (China Standard Time)

Milas Bowman · Answer 3 · Mon Sep 26 2022 23:51:30 GMT+0800 (China Standard Time)

This issue (and many others) should be fixed now. Thanks for reporting and the PR(s) to fix it!