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

RE FAIL: Downloading precompiled headless Chromium binary (stable channel) for AWS Lambda. #17

Open
quantumalchemy opened this issue Jul 26, 2019 · 4 comments

Comments

@quantumalchemy
Copy link

Failed at the @serverless-chrome/[email protected] postinstall script. >>
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @serverless-chrome/[email protected] postinstall: node scripts/postinstall.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @serverless-chrome/[email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-07-26T17_13_00_178Z-debug.log
The command '/bin/sh -c npm install t9tio/cloudquery' returned a non-zero code: 1

@quantumalchemy
Copy link
Author

quantumalchemy commented Jul 29, 2019

update - tried on Docker with node:10.16.0-alpine on aws download chrome but errors.. ->
Downloading precompiled headless Chromium binary (stable channel) for AWS Lambda.
Completed Headless Chromium download.
npm WARN saveError ENOENT: no such file or directory, open '/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.

  • [email protected]
    added 77 packages from 72 contributors and audited 160 packages in 7.759s
    found 0 vulnerabilities

Removing intermediate container 99018088037d
---> 4fad82d16fd0
Step 4/6 : RUN npm run sb
---> Running in 7dbfe536d30c
npm ERR! path /package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-07-29T14_09_46_089Z-debug.log
The command '/bin/sh -c npm run sb' returned a non-zero code: 254

** anyway to get this to work in Docker ? Thanks! Great project!

@timqian
Copy link
Member

timqian commented Jul 29, 2019

seems some issue with serverless/chrome package, I can have a try tomorrow

@timqian
Copy link
Member

timqian commented Jul 30, 2019

npm i works for me
May be network issue on your machine?

@quantumalchemy
Copy link
Author

quantumalchemy commented Jul 30, 2019

yeah Im trying to do this in docker
tried on local network and on a AWS EC2 and getting :

Downloading precompiled headless Chromium binary (stable channel) for AWS Lambda.
Completed Headless Chromium download.
npm WARN saveError ENOENT: no such file or directory, open '/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field. .... Bla Bla

guess this will not install on Docker .. weird
will give it a try on bare metal
Anyway Thanks!

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

No branches or pull requests

2 participants