GitHub user dosubot[bot] added a comment to the discussion: Superset Failed 
taking a screenshot Message: 'chromedriver' executable needs to be in PATH. 
Please see https://sites.google.com/a/chromium.org/chromedriver/home from 
sending email automatically with Alert&Report function

<!-- Greeting -->
Hello, @Bapawin! I'm here to help you with any bugs, questions, and 
contributions. Let's work on solving the issue you're facing.

<!-- Answer -->
I found some similar discussions and issues related to the error you're 
encountering with the 'chromedriver' executable in Superset:

1. [Failed taking a screenshot Message: 'chromedriver' executable needs to be 
in PATH.](https://github.com/apache/superset/discussions/30836) - This 
discussion is unsolved but highlights the same issue you're facing 
<sup>[[1]](https://github.com/apache/superset/discussions/30836)</sup>.

2. [Can't get ALERTS & REPORTS working. Error: Failed taking a screenshot 
Message: 'geckodriver' executable needs to be in 
PATH.](https://github.com/apache/superset/discussions/28698) - This is another 
unsolved discussion with a similar problem 
<sup>[[2]](https://github.com/apache/superset/discussions/28698)</sup>.

To resolve the issue with the 'chromedriver' executable, ensure that it is 
installed and correctly placed in the system's PATH. You can modify your 
Dockerfile to include the installation of `chromedriver` as follows:

```dockerfile
FROM apache/superset:3.1.0

USER root

RUN apt-get update && \
    apt-get install -y wget zip libaio1

RUN export CHROMEDRIVER_VERSION=$(curl --silent 
https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116) && \
    wget -O google-chrome-stable_current_amd64.deb -q 
http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${CHROMEDRIVER_VERSION}-1_amd64.deb
 && \
    apt-get install -y --no-install-recommends 
./google-chrome-stable_current_amd64.deb && \
    rm -f google-chrome-stable_current_amd64.deb
RUN export CHROMEDRIVER_VERSION=$(curl --silent 
https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116) && \
    wget -q 
https://storage.googleapis.com/chrome-for-testing-public/${CHROMEDRIVER_VERSION}/linux64/chromedriver-linux64.zip
 && \
    unzip -j chromedriver-linux64.zip -d /usr/bin && \
    chmod 755 /usr/bin/chromedriver && \
    rm -f chromedriver-linux64.zip

RUN pip install --no-cache gevent psycopg2 redis

USER superset
```

Ensure that the `chromedriver` is located in `/usr/bin` and has the correct 
permissions (`chmod 755`). This will make it available in the PATH for the 
Superset application to use. Additionally, set `WEBDRIVER_TYPE` to `"chrome"` 
in your `superset_config.py` to specify the use of Chrome for taking 
screenshots 
<sup>[[3]](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)</sup>.


<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*

---
<sup>Help Dosu learn! Give it feedback: [Great 
Response](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=great_response)
 | [Irrelevant 
Answer](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=irrelevant_answer)
 | [Incorrect 
Sources](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=incorrect_sources)
 | [Too 
Verbose](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=hallucination)
 | 
[Other](https://app.dosu.dev/response-feedback/17d245bd-cb0a-43bd-bf69-c6984e63fe6a?feedback_type=other)</sup>


GitHub link: 
https://github.com/apache/superset/discussions/33610#discussioncomment-13300822

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to