You should find Puppeteer executes successfully, provided proper Chrome flags are used. Chrome will write into /tmp instead.Īdd your JavaScript to your container with a COPY instruction.

disable-dev-shm-usage – This flag is necessary to avoid running into issues with Docker’s default low shared memory space of 64MB.

For a version of Puppeteer purely for connection, see puppeteer-core. If you’re uncomfortable with this, you’ll need to manually configure working Chrome sandboxing, which is a more involved process. When you install Puppeteer, it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API (customizable through Environment Variables). It’s vital you ensure your Docker containers are strongly isolated from your host. Using these flags could allow malicious web content to escape the browser process and compromise the host. In the end, you should have a list of 3 files, namely, index.js, package-lock.json and package.json, and a nodemodules folder. You’ll also notice that it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API.

no-sandbox and disable-setuid-sandbox – These disable Chrome’s sandboxing, a step which is required when running as the root user (the default in a Docker container). npm install puppeteer This will install Puppeteer from the NPM library.Setting this flag explicitly instructs Chrome not to try and use GPU-based rendering. disable-gpu – The GPU isn’t usually available inside a Docker container, unless you’ve specially configured the host.

Puppeteer js download free