Closed danieldocki closed 5 years ago
@koenhandekyn did you see anything like this when testing your setup?
Can you confirm which version of the gem you have installed?
Can you confirm that the GROVER_NO_SANDBOX
ENV var is definitely set?
Can you confirm which version of the gem you have installed?
grover (0.7.3)
Puppeteer Version
"puppeteer": "^1.18.1",
Can you confirm that the
GROVER_NO_SANDBOX
ENV var is definitely set?
yes, is set
doh sorry that's on me. The README had been updated but I hadn't rolled a new release with the updated ENV flag name. Can you please update to 0.7.4
if you'd prefer not to update, you could use the 'old' ENV name for that flag:
heroku config:set CI=true [--remote yourappname]
(but of course going forward it will require the new GROVER_NO_SANDBOX
ENV var)
i'm assuming it's indeed the env name
@abrom
I updated gem and its working.
Thanks.
2019-07-08T23:50:42.562794+00:00 app[web.1]: [0708/235042.049464:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
I set env to GROVER_NO_SANDBOX=true and added builpack https://github.com/jontewks/puppeteer-heroku-buildpack
what am I doing wrong?