Describe the bug
For environment files, podman-compose passes them to podman with its --env-file option. However, podman/docker and docker-compose process environment files differently: podman/docker doesn't support multi-line environment files, while docker compose supports them (https://github.com/containers/podman/issues/18724#issuecomment-1757162444).
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.
mokibit
commented
1 month ago
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 (https://github.com/containers/podman/issues/18724#issuecomment-1757162444).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.