You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "sfirke (via GitHub)" <gi...@apache.org> on 2025/02/12 18:37:50 UTC

Re: [I] Unable to install Chromedriver using Kubernetes deployment (executable not in PATH) [superset]

sfirke commented on issue #32202:
URL: https://github.com/apache/superset/issues/32202#issuecomment-2654550128

   I'm glad you figured out to use `''` for an unauthenticated SMTP server, we have that [part in the docs](https://superset.apache.org/docs/configuration/alerts-reports/#detailed-config) so I removed it from this issue title to focus things.
   
   Can you build your own image on top of the base Superset image and then ensure there that Chromedriver is getting installed properly? The way you are going about it now should be possible I think but I'm ignorant of Kubernetes/Helm so can't help. Building your own image might be easier to debug.


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org