"Variable is not set" error while trying to run "docker compose pull"

[josedurigon]

Bug description

PS C:\superset\superset> docker compose up -d
time="2024-04-20T21:25:18-03:00" level=warning msg="The "SCARF_ANALYTICS" variable is not set. Defaulting to a blank string."
time="2024-04-20T21:25:18-03:00" level=warning msg="The "CYPRESS_CONFIG" variable is not set. Defaulting to a blank string."
time="2024-04-20T21:25:18-03:00" level=warning msg="The "CYPRESS_CONFIG" variable is not set. Defaulting to a blank string."
validating C:\superset\superset\docker-compose.yml: services.superset-init.env_file.0 must be a string

How to reproduce the bug

Following the steps on documentation
1 - clone the project on github
2 - run docker compose up

Screenshots/recordings

Superset version

master / latest-dev

Python version

3.10

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[TK2575]

Same error occurs on mac, not windows specific

[badf007]

Something that worked for me to for now fix this was to change what the env_file variable received, looks like the format they used to represent the paths is not working correctly with YML format.

Try changing the variables like this, removing both - path elements and just sending 1 path as the input.

env_file: docker/.env # default

Note that you need to do that for all services that use the variable env_file

[josedurigon]

Something that worked for me to for now fix this was to change what the env_file variable received, looks like the format they used to represent the paths is not working correctly with YML format.

Try changing the variables like this, removing both - path elements and just sending 1 path as the input.

env_file: docker/.env # default

Note that you need to do that for all services that use the variable env_file

Hey thanks for trying to help, but it still doesn't work. I get the same messages.

[mistercrunch]

Minimum docker-compose version is 2.24.0 what are you on?

[dlgldgldgld]

In my case, It's resolved after updating docker-compose.
before: 2.16, after: 2.26

[mistercrunch]

TODO: implement some sort of superset check-env command that would check for versions of node, npm, docker, docker-compose and tell you what you need to upgrade.

[josedurigon]

Minimum docker-compose version is 2.24.0 what are you on?

That's it. Worked just fine

[josedurigon]

I've updated my Docker and it ran without any issues. Thank you all for the support