Describe the bug
docker-compose implicitely uses the .env file to populate variables contained in the file passed to env_file, whereas podman-compose does not.
To Reproduce
.env:
.foo:
docker-compose.yml:
version: "3"
services:
example:
image: busybox
env_file: .foo
command: >
sh -c '
set | grep FOO
'
Expected behavior
I would expect podman-compose to behave the same way as docker-compose.
Actual behavior
docker compose up
example-1 | FOO='bar'
podman-compose up
[example] | FOO='$BAR'
Environment:
- OS: Linux
- podman version: 4.9.2
- podman compose version: 1.0.6
Thanks!
Describe the bug
docker-composeimplicitely uses the.envfile to populate variables contained in the file passed toenv_file, whereaspodman-composedoes not.To Reproduce
.env:
.foo:
docker-compose.yml:
Expected behavior
I would expect
podman-composeto behave the same way asdocker-compose.Actual behavior
Environment:
Thanks!