You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:03:57 UTC
Re: [D] SUPERSET ALERT & REPORT: no chrome binary at /usr/bin/google-chrome [superset]
GitHub user dosubot[bot] edited a comment on the discussion: SUPERSET ALERT & REPORT: no chrome binary at /usr/bin/google-chrome
<!-- Greeting -->
Hi @bnprayoga! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
The error means Superset (via Selenium) can't find or run Chrome at `/usr/bin/google-chrome`, even though your shell can. This usually happens because the Celery worker process runs with a different environment or permissions than your shell.
Here’s how to fix it:
1. **Check permissions:** Run `ls -l /usr/bin/google-chrome` and make sure the user running Superset and Celery can execute it.
2. **Version match:** Make sure your Chrome and ChromeDriver versions match exactly. Run `google-chrome --version` and `chromedriver --version` to check.
3. **Configuration:** Superset expects the Chrome binary path in the `WEBDRIVER_CONFIGURATION` dictionary, not just as `CHROME_BINARY_LOCATION`. Update your `superset_config.py` like this:
```python
WEBDRIVER_TYPE = "chrome"
WEBDRIVER_OPTION_ARGS = [
"--force-device-scale-factor=2.0",
"--high-dpi-support=2.0",
"--headless",
"--disable-gpu",
"--disable-dev-shm-usage",
"--no-sandbox",
"--disable-setuid-sandbox",
"--disable-extensions",
]
WEBDRIVER_CONFIGURATION = {
"service": {
"executable_path": "/usr/bin/chromedriver",
"log_output": "/dev/null",
"service_args": [],
"port": 0,
"env": {},
},
"options": {
"capabilities": {},
"preferences": {},
"binary_location": "/usr/bin/google-chrome",
},
}
```
[Reference](https://github.com/apache/superset/discussions/35178)
4. **Restart everything:** After changing config, restart both Superset and all Celery workers so they pick up the new settings.
5. **Environment:** If you’re running Superset and Celery in a virtual environment, make sure both are started from the same shell/environment so they see the same PATH and config.
If you still get errors, check for system restrictions (like SELinux/AppArmor), and confirm that `/usr/bin/google-chrome` is executable by the Superset/Celery user.
If Selenium keeps failing, you can switch to Playwright for screenshots and reports by setting `PLAYWRIGHT_REPORTS_AND_THUMBNAILS = True` in your config and installing the `playwright` Python package. Playwright is often more robust in tricky environments.
Let me know if you need help with any of these steps!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=507513e2-c688-4d2a-b12e-77fc0456a224) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35780#discussioncomment-14746775
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org