Open ricardodomingues10 opened 8 months ago
Defining CHROME_PATH=/usr/bin/chromium also doesn't work. Despite this being the location in the published Debian docker image.
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)
TLDR: Set the env -> PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium
If i get my hands on some time I will debug this.
Thx for thw workaround, unfortunately it does not work for me :( I still get the same error
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:
npm install
) orCan you help me?