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

Not running on Google Cloud Functions #66

Closed
moesalih opened this issue Sep 20, 2019 · 2 comments
Closed

Not running on Google Cloud Functions #66

moesalih opened this issue Sep 20, 2019 · 2 comments

Comments

@moesalih
Copy link

moesalih commented Sep 20, 2019

I'm trying to run this on Google Cloud Functions and it's not working. I get the following error:

Error Error: Failed to launch chrome! [0920/161236.165262:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180. TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

And I did try passing the '--no-sandbox' arg using:

const png = await convert(canvas.svg(), {
	headless: true,
	args: ['--no-sandbox']
})

But I still get the same error. Anyone know what the issue is?

For what it's worth, I am running pupeteer on its own in another Cloud Function and that is working fine.

@paulmelnikow
Copy link

Similarly I haven't been able to get it to work in Heroku (which may mean I adopt a different solution; see my attempts at badges/svg-to-image-proxy#41). This is a Puppeteer issue and I've tried following the instructions at https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-on-heroku, but no luck.

There are some notes on Google Cloud Functions: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-on-google-cloud-functions though it says "it should work." 🤷‍♂

@neocotic
Copy link
Owner

I'm sorry for the incredibly long delay in replying in responding to you but life sometimes gets in the way of OSS development. I thank you for your patience and, although I'm closing this issue out, I hope you'll be glad to know that I hope this issue may be resolved in with today's 0.6.0 release with a huge bump in the version of Puppeteer that's supported.

If you continue to have this problem, please raise a new ticket with complete logs to enable investigation. I hope you can understand my delay.

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

3 participants