-
Notifications
You must be signed in to change notification settings - Fork 485
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
Passing of environment variables does not match behaviour of docker-compose #491
Comments
Just ran into the same issue |
agree |
I've also run into this issue, including the fact that I can't map my variables to my docker-compose values. Eg: ---
version: '3.7'
services:
test:
image: $DIST:$VERSION
container_name: $DIST
environment:
- FOO This build would fail, as podman-compose fails to load the DIST and VERSION while attempting to spin up the container. |
We ran into issues when environment variables had quotes, e.g. |
I had the same issue here. I am used to use something like this with docker-compose:
and it gets the value from the .env file:
with podman-compose it doesn't work. but if I export this variable before I run the podman-compose command, it works just fine. |
When running # docker-compose.yml
version: "3.2"
services:
srv:
environment:
- MY_VAR and # docker-compose.extras.yml
version: "3.2"
srv:
environment:
- MY_VAR=value I get:
|
Also have this issue. For
When running the container, and port 5432 is instead mapped to 35432. |
Any news for this? I also had the problem with podman-compose & mattermost as root when using variables When im using the recommended .env file example and change postgres information, it is not forwarded to the container. How to reproduce:
docker-compose.yml is having this information:
When you hit the command to start: The containers are starting up, but the variables are not forwarded Fix:
Than it works.. had todo this to all other variables too. Docker also "recomment" todo this: https://docs.docker.com/compose/environment-variables/set-environment-variables/
|
Given compose file
and having the
FOO
set in.env
, the variable is not passed into the container. Using- FOO=${FOO}
works but either one works with docker-compose.podman-compose version: 1.0.4
using podman version: 3.4.2
The text was updated successfully, but these errors were encountered: