The Node.js runtime of the App Engine standard environment comes with all system packages needed to run Headless Chrome.
Running Puppeteer in the cloud Running Puppeteer on Google App Engine Treatment for processes with PID=1, which makes it hard to terminate Chrome Since the DockerfileĪdds a pptr user as a non-privileged user, it may not have all the necessary privileges.ĭumb-init is worth checking out if you'reĮxperiencing a lot of zombies Chrome processes sticking around. With docker run -cap-add=SYS_ADMIN when developing locally. Seeing other weird errors when launching Chrome? Try running your container This will write shared memory files into /tmp instead of /dev/shm. To work around this, try running without the flag:Ĭonst browser = await puppeteer. Puppeteer passes -disable-extensions flag by default and will fail to launch when such policies are active. Some chrome policies might enforce running Chrome/Chromium Running Puppeteer on AWS EC2 instance running Amazon-LinuxĬhrome headless doesn't launch on Windows.Running Puppeteer on Google Cloud Functions.Chrome is downloaded but fails to launch on Node.js 14.Chrome headless disables GPU compositing.Chrome headless doesn't launch on Windows.