Multi-line environment files are not correctly processed #908
Labels
bug
Something isn't working
Comments
hedayat
added a commit
to hedayat/podman-compose
that referenced
this issue
Apr 8, 2024
Signed-off-by: Hedayat Vatankhah <hedayat.fwd@gmail.com>
hedayat
added a commit
to hedayat/podman-compose
that referenced
this issue
May 7, 2024
Signed-off-by: Hedayat Vatankhah <hedayat.fwd@gmail.com>
mokibit
pushed a commit
to mokibit/podman-compose
that referenced
this issue
May 26, 2024
Signed-off-by: Hedayat Vatankhah <hedayat.fwd@gmail.com>
mokibit
pushed a commit
to mokibit/podman-compose
that referenced
this issue
May 26, 2024
Signed-off-by: Hedayat Vatankhah <hedayat.fwd@gmail.com>
p12tic
pushed a commit
to mokibit/podman-compose
that referenced
this issue
May 28, 2024
Signed-off-by: Hedayat Vatankhah <hedayat.fwd@gmail.com>
|
Fixed in #949. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
For environment files, podman-compose passes them to
podmanwith its--env-fileoption. However,podman/dockeranddocker-composeprocess environment files differently:podman/dockerdoesn't support multi-line environment files, while docker compose supports them (containers/podman#18724 (comment)).Expected behavior
Properly support multi-line env files
Actual behavior
Just passes env-files to podman, which doesn't support multi-line env vars, as apparently docker also doesn't support them too.
** Implementation **
I found that it can be easily implemented (parse env file with dotenv, and pass variables to podman), and I'll open a PR to fix it too.
The text was updated successfully, but these errors were encountered: