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
docker compose config no longer populates the environment attribute with values from an env file.
This change broke a few of our deployment pipelines, since we prefer to ship only the compose file generated by the config command, rather than shipping the compose file and the env file.
prior to v2.24.7 we were able to run docker compose --file foo.yml config and get the following output:
name: foo
services:
foo_serv:
environment:
BAR: baz
FOO: bar
image: debian:latest
networks:
default: null
networks:
default:
name: foo_default
notice the environment attribute is populated with our environment variables from the env file. This allowed us to ship a single compose file with all of our env vars defined.
However, since compose 2.24.7, we get this output:
Description
docker compose config
no longer populates theenvironment
attribute with values from an env file.This change broke a few of our deployment pipelines, since we prefer to ship only the compose file generated by the
config
command, rather than shipping the compose file and the env file.Is there any way to get this old behavior back?
Steps To Reproduce
given these two files:
foo.yml
:and
foo.env
:prior to v2.24.7 we were able to run
docker compose --file foo.yml config
and get the following output:notice the
environment
attribute is populated with our environment variables from the env file. This allowed us to ship a single compose file with all of our env vars defined.However, since compose 2.24.7, we get this output:
it no longer populates the
environment
attribute at all, instead we have theenv_file
attribute that points to the env file.Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: