dosubot[bot] commented on issue #34441:
URL: https://github.com/apache/superset/issues/34441#issuecomment-3163699636

   <!-- Answer -->
   If the config still isn't loading, let's double-check a few things that 
often cause this in Docker Compose with Superset 5:
   
   1. Make sure you do NOT set SUPERSET_CONFIG_PATH in your environment or 
docker-compose.yml—this can break Docker's config override flow. Remove it 
everywhere and restart your containers. The recommended way is to rely on the 
default config loading, not this variable [[docker-compose config 
docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md)].
   
   2. Place your config as superset_config_docker.py in 
./docker/pythonpath_dev/ on your host. After restarting, it should appear 
inside the container at /app/pythonpath/superset_config_docker.py (or 
/app/docker/pythonpath_dev/superset_config_docker.py depending on your image). 
You can check this by running:
      ```
      docker exec -it <superset_container_name> ls -l /app/pythonpath
      docker exec -it <superset_container_name> ls -l /app/docker/pythonpath_dev
      ```
      Confirm the file is present and readable.
   
   3. Check your Superset logs for either "Loaded your Docker configuration at 
[...]" (success) or "Using default Docker config..." (failure). If you don't 
see the "Loaded..." message, your override isn't being picked up 
[[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py)].
   
   4. To confirm if the config is loaded at all, add raise Exception("test 
config load") at the very top of superset_config_docker.py, restart Superset, 
and check the logs for this error. If you don't see it, the config isn't being 
loaded 
[[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/pythonpath_dev/superset_config.py)].
   
   5. If the config is loading, add a print or logging statement inside your 
FLASK_APP_MUTATOR function to confirm it's executed at startup 
[[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/initialization/__init__.py)].
   
   If after all this your config still isn't loading, please share:
   - The output of the ls commands above
   - The relevant lines from your Superset startup logs
   - Your docker-compose.yml config section for the superset service
   
   This will help pinpoint exactly where the config loading is breaking down.
   
   
   <!-- 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/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/d890b44a-9f60-4369-ac72-b0edb98d5048?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34441)


-- 
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]

Reply via email to