Alerts & Reports fail on ARM64: Selenium cannot obtain Chrome/Firefox driver (“Unsupported platform/architecture linux/aarch64”) #36457
Replies: 2 comments
-
|
This is a known limitation: Selenium Manager does not support ARM64, so Superset fails to generate screenshots for Alerts & Reports on ARM environments, even if you manually install the browser and driver. Superset does not currently expose a config to override the WebDriver executable path to bypass Selenium Manager, so manual driver installation alone is not enough [source]. The recommended and robust solution is to switch to Playwright for screenshot generation. Playwright supports ARM64 and is now the preferred backend for Superset screenshots [source]:
No other configuration changes are needed. Alerts & Reports will continue to work as usual, and screenshot-based formats (PNG, PDF) will be functional on ARM64. If you need to stick with Selenium, there is currently no supported way to bypass Selenium Manager for the driver executable in Superset’s config. Playwright is the recommended path forward for ARM environments. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Hi i did tried by adding to values.yaml the following: I still get the following issue: Im doing something wrong ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug description
When running Apache Superset on ARM64 (AWS Graviton / linux/aarch64), all Alerts & Reports that require screenshot generation fail with the following Selenium error:
Superset attempts to use Selenium Manager to automatically download a Chrome or Firefox WebDriver. Selenium Manager does not ship drivers for ARM64, which results in:
• Unable to obtain driver for chrome
• Unable to obtain driver for firefox
• Reports failing with ReportScheduleScreenshotFailedError
This makes Alerts & Reports completely non-functional on ARM environments, even when Chromium + Chromedriver are installed manually inside the container.
I can just sent it to a Slack channel as a CSV , not PNG not no other.
Environment
• Architecture: ARM64 (aarch64) — AWS Graviton worker nodes
• Superset version: 3.x / latest Docker image
• Python: 3.10
• Selenium: bundled with official Superset image
• Chromium + chromedriver manually installed in /usr/bin
• Reports & Alerts enabled and Celery working
• Error occurs in both superset-worker and superset-celerybeat
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
Beta Was this translation helpful? Give feedback.
All reactions