You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there a bug that were on docker-compose some time ago.
As stated here, the variables declared on the dotenv can be quoted or not. A simple string does not require anything, as well as an integer, but with a whitespace we need to use some kind of quotes.
NAME="Mike White"
AGE=33
Within a container created by docker compose, this happens:
root@65e1bca70a68:/app# echo $NAME
Mike White
root@65e1bca70a68:/app# echo $AGE
33
BUT, within a podman container created by podman-compose, this happens:
Describe the bug
I think there a bug that were on docker-compose some time ago.
As stated here, the variables declared on the dotenv can be quoted or not. A simple string does not require anything, as well as an integer, but with a whitespace we need to use some kind of quotes.
Within a container created by docker compose, this happens:
BUT, within a podman container created by podman-compose, this happens:
To Reproduce
.env
docker-compose.yaml
podman-compose up -d
Enter the container interactively, type echo $NAME
Expected behavior
The double quotes should have been stripped
Actual behavior
The double quotes are there
Output
Environment:
The text was updated successfully, but these errors were encountered: