superset icon indicating copy to clipboard operation
superset copied to clipboard

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

Open josedurigon opened this issue 10 months ago • 4 comments

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

image

image

image

Superset version

master / latest-dev

Python version

3.10

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

  • [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [X] 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.

josedurigon avatar Apr 21 '24 01:04 josedurigon

Same error occurs on mac, not windows specific

TK2575 avatar Apr 21 '24 03:04 TK2575

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

badf007 avatar Apr 22 '24 15:04 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

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

josedurigon avatar Apr 22 '24 19:04 josedurigon

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

mistercrunch avatar Apr 23 '24 01:04 mistercrunch

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

dlgldgldgld avatar May 01 '24 14:05 dlgldgldgld

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.

mistercrunch avatar May 01 '24 15:05 mistercrunch

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

That's it. Worked just fine

josedurigon avatar May 01 '24 18:05 josedurigon

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

josedurigon avatar May 01 '24 18:05 josedurigon