Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Locate Chromium #108

Open
ricardodomingues10 opened this issue Mar 12, 2024 · 3 comments
Open

Unable to Locate Chromium #108

ricardodomingues10 opened this issue Mar 12, 2024 · 3 comments

Comments

@ricardodomingues10
Copy link

I tried this command: docker run -p 3000:3000 lissy93/web-check, and encountered this problem.

Error details tech-stack:
Could not find Chromium (rev. 1095492). This can occur if either:

  1. you did not perform an installation before running the script (e.g. npm install) or
  2. your cache path is incorrectly configured (which is: /root/.cache/puppeteer).
    For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.

Can you help me?

@m4teh
Copy link

m4teh commented May 5, 2024

Defining CHROME_PATH=/usr/bin/chromium also doesn't work. Despite this being the location in the published Debian docker image.

@Error00101
Copy link

Error00101 commented Aug 23, 2024

Had the same issue.
@m4teh
Defining the 'CHROME_PATH' does not work as it is already defined inside the container (just run env inside the container -> you will see it is defined)

however I dug through some of the sourcecode. ( -> API -> tech-stack -> wappalyzer(v6.10) ->puppeteer)
puppeteer has some documentation where I found a few Interesting thing:
PUPPETEER_CACHE_DIR -> nope
PUPPETEER_EXECUTABLE_PATH -> YES this is it (Somewhere through the chain the CHROME_PATH gets lost and now replaced with nothing - didnt look where but semms to be solvable)

Screenshots of it not working/Working with the coresponding Compose files not working :(

grafik

now working :)
grafik

TLDR:
Set the env -> PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium

If i get my hands on some time I will debug this.

@b1nary-b0b
Copy link

Thx for thw workaround, unfortunately it does not work for me :( I still get the same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants