Closed joemaller closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it had not recent activity during the stale period.
Description
This issue is a reduced test case:
docker compose
throws errors on some .env files which prevents containers from running. The same .env files work correctly in versions of prior versions ofdocker-compose
(pre v2).Related to #7624, #8879 & #8763
Steps to reproduce the issue:
docker-compose config
(works)docker compose config
(error)note: Use Docker Compose V2 must be unchecked in Docker's General Preferences to access the old docker-compose binary.
Describe the results you received:
docker compose config
throws this error:unexpected character "@" in variable name near "user@host\n"
Describe the results you expected:
.env file is parsed, containers run normally, same input/output as
docker-compose
pre-v2.Additional information you deem important (e.g. issue happens only occasionally):
The .env file validates without errors using python-dotenv and Rust's dotenv-linter, and can be loaded by the dotenv node.js package, with or without quoting the value.
Running
docker-compose up
shows the environment including the value from .env. If the .env value is quoted, bothdocker compose up
anddocker-compose up
return identical results. The property's value should not need quotes.The reported errors were reproduced on WSL2 and macOS.
Output of
docker compose version
:Output of
docker info
:Additional environment details:
Use Docker Compose V2 is unchecked in Docker's General Preferences,
docker-compose --version
returns