intellisession opened a new issue, #34723: URL: https://github.com/apache/superset/issues/34723
### Bug description TLDR: `SUPERSET_LOAD_EXAMPLES=no docker compose -f docker-compose-image-tag.yml up` is a solution/work that worked for Superset 5.0.0 and Docker Desktop 4.44.1 (201842). I followed the instructions here https://superset.apache.org/docs/quickstart/: ``` # Enter the repository you just cloned $ cd superset # Set the repo to the state associated with the latest official version $ git checkout tags/5.0.0 # Fire up Superset using Docker Compose $ docker compose -f docker-compose-image-tag.yml up ``` Before I ran the `docker compose` command, I created a `docker/.env-local` containing SUPERSET_LOAD_EXAMPLES=no. I believe this is what the documentation says to do here essentially https://superset.apache.org/docs/installation/docker-compose/#configuring-further, and that's what this stackoverflow answer says too https://stackoverflow.com/a/79412095/8061073. NOTE: I ran the `env` command in all of the containers, and I see that `SUPERSET_LOAD_EXAMPLES` gets set to `no`. (That is, `SUPERSET_LOAD_EXAMPLES` is not set to `yes` anywhere.) However, this did not work. The examples still get loaded. Worse, I had tried to manually delete all of the examples, but when I restarted the containers (e.g. running `docker compose -f docker-compose-image-tag.yml up` after having first stopped them), the examples get loaded again... I also recall trying to comment out the `SUPERSET_LOAD_EXAMPLES` variable altogether from `docker/.env`, but that did not work either. However, when I remove the line `SUPERSET_LOAD_EXAMPLES: "${SUPERSET_LOAD_EXAMPLES:-yes}"` in the docker-compose file, the value in `.env-local` gets picked up, as expected. Thus, the right way to avoid loading examples is not to set `SUPERSET_LOAD_EXAMPLES=no` in `.env-local`, but to set the variable from the host shell essentially: `SUPERSET_LOAD_EXAMPLES=no docker compose -f docker-compose-image-tag.yml up` To prevent people from running into this issue in the future, we should do one of the following: 1. Remove `SUPERSET_LOAD_EXAMPLES: "${SUPERSET_LOAD_EXAMPLES:-yes}"` from the compose file. 2. Remove `SUPERSET_LOAD_EXAMPLES` from the `docker/.env` file (to prevent people from thinking that modifiying it there will have any effect), and change the documentation at https://superset.apache.org/docs/installation/docker-compose/#configuring-further and the Stackoverflow answer at https://stackoverflow.com/a/79412095/8061073 telling people to prefix `SUPERSET_LOAD_EXAMPLES=no ` to their `docker compose` command. ### Screenshots/recordings _No response_ ### Superset version 5.0.0 ### Python version Not applicable ### Node version 18 or greater ### Browser Chrome ### Additional context Docker version is: `4.44.1 (201842)` ### 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. - [x] 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
