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
Puppeteer should check platform compatibility when running #2996
Comments
@kingio Chromium is compiled for x86_64, which I believe is not runnable on i686. We don't have any 32 bit builds, and there are no plans to add any. Sorry for the inconvenience. |
Shouldn't puppeteer do a requirement check before installing itself? You would avoid issues like this |
@kingio this would be nice to have; I'd be happy to review a PR. |
Actually, we should rather do this in runtime on |
Oh wow... I've been trying to get this to work for hours... I kept thinking i had forgotten to place a parenthesis somewhere .-. |
@aslushnikov Do you mind if I take a stab at this? can you give me some pointers on were would be a good place to start? Thanks |
Looks like in node, Would it be safe to assume that the 32bit version of node should not be able to launch Chromium? Otherwise, I can basically do what this library does to detect the architecture of the OS. |
what happened here still no solutions ? |
I am having problems with launching browser too. Can puppeteer work with 32 bit chromium by changing the executablePath : |
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
npm i puppeteer
What is the expected result?
Working chrome
What happens instead?
(node:14901) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome! /var/www/spiderman/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: 1: /var/www/spiderman/node_modules/puppeteer/.local-chromium/linux-575458/chrome-linux/chrome: Syntax error: word unexpected (expecting ")")
If i manually run that chrome, it says
cannot execute binary file: Exec format error
The text was updated successfully, but these errors were encountered: