Skip to content
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

Error response from daemon: invalid environment variable: =::=::\ #216

Open
bronvic opened this issue Mar 24, 2023 · 2 comments
Open

Error response from daemon: invalid environment variable: =::=::\ #216

bronvic opened this issue Mar 24, 2023 · 2 comments

Comments

@bronvic
Copy link

bronvic commented Mar 24, 2023

I'm trying to add an env file to my configuration and see an error: Error response from daemon: invalid environment variable: =::=::\
My configuration is a pytest run using docker-compose interpretator
2023-03-24_16-44

The thing is that I can use this file when running docker-compose manually. The error is present even if env file is empty
2023-03-24_16-49

I'm working on Windows using WSL2

@TimChild
Copy link

TimChild commented Apr 26, 2024

I also just started having this problem. I think from upgrading pycharm to 2024.1.

Anyone know a solution for this?

EnvFile: 3.4.2
PyCharm: 2024.1
OS: Windows but running remote interpreter in WSL2

image

With "Enable EnvFile" in run config unticked, the error does not show up (but also env vars aren't loaded obviously...)

@TimChild
Copy link

Well, a possible solution... Don't use EnvFile at all... I've not noticed the option for "Paths to '.env' files" before, but it seems to work. Maybe it was recently introduced in Pycharm?

By the way, you might need to enable it in the "Modify options" dropdown at the top right of the window.

It's definitely not as nice as EnvFile because it immediately got tripped up on a commented out env var I had, but might be a solution for some people.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants