dosubot[bot] commented on issue #34723: URL: https://github.com/apache/superset/issues/34723#issuecomment-3193764621
<!-- Greeting --> Hi @intellisession! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Your analysis is correct: setting `SUPERSET_LOAD_EXAMPLES=no` in `docker/.env-local` should override the default in `docker/.env`, as documented in the official Superset Docker Compose guide. However, if the compose file explicitly sets `SUPERSET_LOAD_EXAMPLES: "${SUPERSET_LOAD_EXAMPLES:-yes}"` in the `environment` section, this can override values from both `.env` and `.env-local`, leading to the behavior you observed. In this case, only setting the variable in the host shell (e.g., `SUPERSET_LOAD_EXAMPLES=no docker compose ...`) reliably overrides everything else, because host shell variables always take precedence in Docker Compose’s variable resolution order [docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/docker-compose.mdx). The `env_file` directive in the compose file is designed to merge `.env` and `.env-local`, with `.env-local` overriding `.env` for duplicate keys [compose file](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker-compose-image-tag.yml). But if the variable is also set explicitly in the `environment` section, that value takes priority, which can prevent `.env-local` from working as intended. Your proposed solutions are valid: removing the explicit `SUPERSET_LOAD_EXAMPLES` line from the compose file or updating the documentation to recommend setting the variable in the host shell would both resolve this confusion. There are no recent changes or issues addressing this, so a documentation update would help others avoid this pitfall [docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/docker-compose.mdx). For now, the most reliable way to prevent example data from loading is to prefix your compose command with `SUPERSET_LOAD_EXAMPLES=no`. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/236d497b-995d-47ca-9698-7ef5212beaa1?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34723) -- 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]
