GitHub user dosubot[bot] added a comment to the discussion: Sending scheduled report via email
<!-- Answer --> You can use Chromium from the Debian repositories for Superset scheduled report screenshots—just set `WEBDRIVER_TYPE = "chrome"` in your config and make sure both Chromium and the matching ChromeDriver are installed in your worker container. Superset's code treats Chromium and Chrome identically for Selenium; the only requirement is that the driver and browser versions match, and you may need to set the `binary_location` if the Chromium binary isn't in the default path. This setup is widely used and works reliably, but it's not officially documented or guaranteed by Superset maintainers, so you should verify it in your environment ([reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/webdriver.py)). Here’s a minimal working Dockerfile example for a Superset worker with Chromium and ChromeDriver: ```dockerfile FROM apache/superset:latest USER root # Install Chromium and dependencies RUN apt-get update && \ apt-get install -y chromium chromium-driver && \ ln -sf /usr/bin/chromium /usr/bin/chrome && \ ln -sf /usr/bin/chromium-driver /usr/bin/chromedriver USER superset ``` And in your `superset_config_docker.py`: ```python WEBDRIVER_TYPE = "chrome" WEBDRIVER_OPTION_ARGS = [ "--headless", "--disable-gpu", "--disable-dev-shm-usage", "--no-sandbox", "--disable-setuid-sandbox", "--disable-extensions", ] WEBDRIVER_CONFIGURATION = { "service": { "executable_path": "/usr/bin/chromedriver", "log_path": "/dev/null", "service_args": [], "port": 0, "env": {}, }, "options": { "capabilities": {}, "preferences": {}, "binary_location": "/usr/bin/chromium", # or leave empty if default }, } ``` This setup works for most users. If you run into issues, double-check that the versions of Chromium and ChromeDriver match, and that the paths are correct. For more details and troubleshooting tips, see the [official Superset docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/configuration/alerts-reports.mdx). <!-- 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/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/da75f9c1-6192-45fe-9db4-3c630eb319ec?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/discussions/35178) GitHub link: https://github.com/apache/superset/discussions/35178#discussioncomment-14443722 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
