dosubot[bot] commented on issue #34796: URL: https://github.com/apache/superset/issues/34796#issuecomment-3210931429
<!-- Greeting --> Hi @bluemalkin! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Superset’s config loading for Celery workers hasn’t changed between v4.0.2 and v5.0.0—the worker should load your custom superset_config.py if it’s mounted and referenced correctly, and the log message confirms it’s being loaded. If the worker is still using the default WEBDRIVER_BASEURL (http://0.0.0.0:8080), this usually points to a container/Helm setup issue, not a Superset bug. Double-check that your superset_config.py is mounted in every pod (web, worker, beat) and that environment variables like SUPERSET_CONFIG_PATH and PYTHONPATH are set so the config is found on startup. If you’re using Helm, make sure your values.yaml mounts the config in all relevant containers and sets the env vars for all Superset processes [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py). For screenshot failures, Superset 5.0.0 works best with WEBDRIVER_TYPE set to "chromium" or "chrome" (not "firefox"), and option args like `--headless`, `--disable-gpu`, `--disable-dev-shm-usage`, `--no-sandbox`, and `--disable-setuid-sandbox`. You may also want to use the WEBDRIVER_CONFIGURATION dictionary to specify the executable path and options for your WebDriver, which helps avoid DNS and connection errors in containerized environments [source](https://github.com/apache/superset/discussions/34053). If page loads are slow, increase SCREENSHOT_LOCATE_WAIT and SCREENSHOT_LOAD_WAIT to 30 and 60 seconds [source](https://github.com/apache/superset/issues/33602). If you’re still seeing issues, check that your container image includes the necessary browser and driver binaries, and that all pods have access to the same config and binaries. Let me know if you want example config snippets or troubleshooting steps for Helm! <!-- 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/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/131d9ca8-3945-46a5-b863-09fc57d9f107?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/34796) -- 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]
