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
.env defines variables to be used for interpolation, not os.Environment. This used to be set as os.Env due to a design issue in earlier versions. I suggest you source this .env file to populate os.Env before you run compose.
We could introduce an explicit content attribute for secrets so that one can write:
secrets:
MY_SECRET:
content: ${MY_SECRET}
doing so, variables interpolation from .env would set secret value
Description
Previously in version v2.27.1 this worked:
In
.env
:In docker compose yaml:
However in after updating to v2.28.1 the secret is not loaded correctly from
.env
file anymore causing builds that rely on the secret to fail.Steps To Reproduce
Define a secret in
.env
file and try to use it in docker compose.Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: