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

npm package contains wrong chrome binary for Linux ARM (Raspberry Pi 3, Raspbian) #2124

Closed
ujay68 opened this issue Feb 28, 2018 · 6 comments

Comments

@ujay68
Copy link

ujay68 commented Feb 28, 2018

For Linux ARM, the npm package contains a wrong chrome binary.

Tell us about your environment:

  • Puppeteer version: 1.1.1
  • Platform / OS version: Raspberry Pi 3 / Raspbian Stretch, fully updated as of 2018-02-28
  • Node.js version: v8.9.4

What steps will reproduce the problem?

$ npm i --save puppeteer
$ ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome
-bash: ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome: cannot execute binary file: Exec format error
$ file ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome
./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not stripped

@secreter
Copy link

mark,the same

@scissorsneedfoodtoo
Copy link

scissorsneedfoodtoo commented Mar 29, 2018

I had a similar problem about a month ago. Check out @Austinb's comment toward the bottom of issue #550 for a workaround.

@Austinb
Copy link

Austinb commented Mar 29, 2018

You cant use the chromium built library from puppeteer on PI. You need to update your built in chromium on the PI and use that one in your code. See @scissorsneedfoodtoo's comment above.

For builds on ARM they should disable building of the chromium by default since it does not work or fix it so it will run. Confuses many people it seems.

@napolux
Copy link

napolux commented Apr 8, 2018

@Austinb any step-by-step way to fix this?

@Austinb
Copy link

Austinb commented Apr 8, 2018

See #550

@aslushnikov
Copy link
Contributor

Dupe of #550.

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

6 participants