Menu
I deployed an app on heroku, and I added the Puppeteer Heroku buildpack.
After a succesful redeployment, I tried to run it and it fails. Using heroku logs -t, I get this error message:
2018-09-07T13:16:10.870497+00:00 app[web.1]: Error: Failed to launch chrome!
2018-09-07T13:16:10.870512+00:00 app[web.1]: [0907/131610.045486:FATAL:zygote_ho
st_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chro
mium.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.
930
Installs dependencies needed in order to run puppeteer on heroku. Be sure to include { args: ['--no-sandbox'] } in your call to puppeteer.
Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium.
Here is what worked for me. First, I clear all my buildpacks and then I added the puppeteer-heroku-buildpack and the heroku/nodejs one:
$ heroku buildpacks:clear $ heroku buildpacks:add --index 1 https://github.com/jontewks/puppeteer-heroku-buildpack $ heroku buildpacks:add --index 1 heroku/nodejs Then, add the following args to the puppeteer launch function:
const browser = await puppeteer.launch({ 'args' : [ '--no-sandbox', '--disable-setuid-sandbox' ] }); Finally, deploy it back to Heroku:
$ git add . $ git commit -m "Fixing deployment issue" $ git push heroku master You should be able to solve this issue by passing the --no-sandbox and --disable-setuid-sandbox flags to puppeteer.launch():
const browser = await puppeteer.launch({
args: [
'--no-sandbox',
'--disable-setuid-sandbox',
],
});
If this does not work, you may want to read the official Puppeteer troubleshooting guide: Running Puppeteer on Heroku.
20
This answer is fantastic, but in the interests of a minimal, runnable example I thought I'd share my complete code and workflow for getting up and running with a Puppeteer-based web app.
See this answer for a simple scheduler and a clock process version (although all three approaches can coexist in one app without doing anything special).
package.json:{
"name": "test-puppeteer",
"version": "1.0.0",
"description": "",
"scripts": {
"start": "node index.js"
},
"author": "",
"license": "ISC",
"dependencies": {
"express": "^4.17.1",
"puppeteer": "^9.1.1"
}
}
Procfile:web: node index.js
index.js:const express = require("express");
const puppeteer = require("puppeteer");
const app = express();
app.set("port", process.env.PORT || 5000);
const browserP = puppeteer.launch({
args: ["--no-sandbox", "--disable-setuid-sandbox"]
});
app.get("/", (req, res) => {
// FIXME move to a worker task; see https://devcenter.heroku.com/articles/node-redis-workers
let page;
(async () => {
page = await (await browserP).newPage();
await page.setContent(`<p>web running at ${Date()}</p>`);
res.send(await page.content());
})()
.catch(err => res.sendStatus(500))
.finally(() => page.close())
;
});
app.listen(app.get("port"), () =>
console.log("app running on port", app.get("port"))
);
Install Heroku CLI and create a new app with Node and Puppeteer buildpacks (see this answer):
heroku create
heroku buildpacks:add --index 1 https://github.com/jontewks/puppeteer-heroku-buildpack -a cryptic-dawn-48835
heroku buildpacks:add --index 1 heroku/nodejs -a cryptic-dawn-48835
(replace cryptic-dawn-48835 with your app name)
Deploy:
git init
git add .
git commit -m "initial commit"
heroku git:remote -a cryptic-dawn-48835
git push heroku master
Verify that it worked with curl https://cryptic-dawn-48835.herokuapp.com. You should see something like
<html><head></head><body><p>web running at Wed May 19 2021 02:12:48 GMT+0000 (Coordinated Universal Time)</p></body></html>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
