dosubot[bot] commented on issue #37127: URL: https://github.com/apache/superset/issues/37127#issuecomment-3792383167
<!-- Answer --> This is indeed a configuration/environment issue, not a Superset bug. For the Celery Beat permission error: make sure all Superset containers (web, worker, beat) share the same Docker named volume for `/app/superset_home`, and that the user running the Beat process has write access to that directory. Running as `root` or ensuring the volume is owned by the container user will resolve this. Host-mounted directories with mismatched ownership are a common cause of this error. For the Selenium screenshot error (`Process unexpectedly closed with status 255`): your worker/beat image must include all required browser dependencies. The official images do not ship with Firefox/geckodriver by default. You need to extend your Dockerfile to install both Firefox and geckodriver (or switch to Chromium/ChromeDriver and set `WEBDRIVER_TYPE = "chrome"` in your config). You can verify installation inside the container with `firefox --headless` and `geckodriver --version`. If you want to use Chrome/Chromium, install both and set the recommended Chrome options for headless operation in Docker. See [this discussion for a working Dockerfile snippet and config](https://github.com/apache/superset/discussions/31783). Finally, your secret key was exposed—rotate it immediately for security. If you want, I can review your Dockerfile or config for any remaining issues. <!-- 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/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2f12ddc0-c986-4a3a-9183-215b43c0ea64?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20indeed%20a%20configuration/environment%20issue%2C%20not%20a%20Superset%20bug.%0A%0AFor%20the%20Celery%20Beat%20permission%20error%3A%20make%20sure%20all%20Superset%20containers%20%28web%2C%20worker%2C%20beat%29%20share%20the%20same%20Docker%20named%20volume%20for%20%60/app/superset_home%60%2C%20and%20that%20the%20user%20running%20the%20Beat%20process%20has%20write%20access%20to%20that%20directory.%20Running%20as%20%60root%60%20or%20ensuring%20the%20volume%20is%20owned%20by%20the%20container%20user%20will%20resolve%20this.%20Host-mounted%20directories%20with%20mismatched%20ownership%20are%20a%20common%20cause%20of%20this%20error.%0A%0AFor%20the%20Selenium%20screenshot%20error%20%28%60Process%20unexpectedly%20closed%20with%20status%20255% 60%29%3A%20your%20worker/beat%20image%20must%20include%20all%20required%20browser%20dependencies.%20The%20official%20images%20do%20not%20ship%20with%20Firefox/geckodriver%20by%20default.%20You%20need%20to%20extend%20your%20Dockerfile%20to%20install%20both%20Firefox%20and%20geckodriver%20%28or%20switch%20to%20Chromium/ChromeDriver%20and%20set%20%60WEBDRIVER_TYPE%20%3D%20%22chrome%22%60%20in%20your%20config%29.%20You%20can%20verify%20installation%20inside%20the%20container%20with%20%60firefox%20--headless%60%20and%20%60geckodriver%20--version%60.%20If%20you%20want%20to%20use%20Chrome/Chromium%2C%20install%20both%20and%20set%20the%20recommended%20Chrome%20options%20for%20headless%20operation%20in%20Docker.%20See%20%5Bthis%20discussion%20for%20a%20working%20Dockerfile%20snippet%20and%20config%5D%28https%3A//github.com/apache/superset/discussions/31783%29.%0A%0AFinally%2C%20your%20secret%20key%20was%20exposed%E2%80%94rotate%20it%20immediately%20for%20security.%0A%0AIf%20you%20want%2C%20I %20can%20review%20your%20Dockerfile%20or%20config%20for%20any%20remaining%20issues.) [](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/37127) -- 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]
