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
When a included compose file defines a secret where the source is an environment variable and this environment variable is set,
the include will populate the content property, which is not allowed.
Run compose config with the include.yaml file and the FOO var set.
FOO=bar docker compose -f include.yaml config
This will fail with:
validating /home/ambros/dev/issue/include.yaml: secrets.foo_secret Additional property content is not allowed
Expected behavior
I expected that the include statement does not populate the content property and this setup should work. The setup works as expected if the environment variable is not set or the compose.yaml file is used directly. This also worked in the pervious compose version v2.28.1.
Description
When a included compose file defines a secret where the source is an environment variable and this environment variable is set,
the include will populate the
content
property, which is not allowed.Reproduce
Create the following two compose files:
Run
compose config
with theinclude.yaml
file and theFOO
var set.This will fail with:
Expected behavior
I expected that the include statement does not populate the
content
property and this setup should work. The setup works as expected if the environment variable is not set or thecompose.yaml
file is used directly. This also worked in the pervious compose version v2.28.1.docker version
docker info
Additional Info
No response
The text was updated successfully, but these errors were encountered: