Description
I'm extracting informations about docker-compose.yml files using docker compose config.
I would expect this command to be rather dumb, but it looks like it tries to fully load the config.
Using the --images argument should not require an env_file, in fact the env_file is only required to populate service's environment and this is not required to display the list of images.
Not that none of --no-consistency, --no-interpolate, --no-normalize and --no-path-resolution bypass this issue.
Steps To Reproduce
- Given the following
docker-compose.yml file:
version: "3"
services:
test:
image: hello-world:latest
env_file:
- .env
- Running
docker compose config --images
- Outputs:
Failed to load /tmp/a/.env: open /tmp/a/.env: no such file or directory with return code 14
Compose Version
❯ docker compose version
Docker Compose version v2.21.0
### Docker Environment
```Text
I doubt this is relevant.
Anything else?
I could not find documentation about return codes for the docker compose config command.
Description
I'm extracting informations about
docker-compose.ymlfiles usingdocker compose config.I would expect this command to be rather dumb, but it looks like it tries to fully load the config.
Using the
--imagesargument should not require anenv_file, in fact theenv_fileis only required to populateservice'senvironmentand this is not required to display the list of images.Not that none of
--no-consistency,--no-interpolate,--no-normalizeand--no-path-resolutionbypass this issue.Steps To Reproduce
docker-compose.ymlfile:docker compose config --imagesFailed to load /tmp/a/.env: open /tmp/a/.env: no such file or directorywith return code14Compose Version
Anything else?
I could not find documentation about return codes for the
docker compose configcommand.