-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accents in unquoted environment variables with spaces cause Compose v2 to fail #8741
Comments
+1 Any environment variable value with |
Seems related to #8763 |
See also #8507 |
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
In a
.env
file, if there is a variable with a space, no quotes, and accents in the word(s) after the space, Compose refuses to start, with an error like the following one:Steps to reproduce the issue:
Create the following files:
Then
docker-compose up
.Describe the results you received:
With Compose v1, it works correctly.
With Compose v2, I get the following error message and Compose refuses to start the stack:
Describe the results you expected:
Stack starts correctly.
Additional information you deem important (e.g. issue happens only occasionally):
Note that this only happens when the accents are AFTER the space, and if the variable is NOT quoted.
Output of
docker compose version
:Similar or related issues:
This could be related to #8626 and/or #8740, which are also related to
.env
parsing in Compose v2.However, since it's a different error behavior altogether, I'm opening a separate issue to make sure it's tracked properly.
Thanks!
The text was updated successfully, but these errors were encountered: