To fix, you'll need to install the missing dependencies and the latest Chromium The bundledĬhromium that Puppeteer installs is missing the necessary shared library Getting headless Chrome up and running in Docker can be tricky. Instructions below might be still helpful if you are building your own image. Starting from v16.0.0 we are shipping a Docker image via the In a Docker container until v3.0.x - see our historicalįor reference. 👋 We used Cirrus Ci to run our tests for Puppeteer To fix this, set jest -maxWorkers=2 in your test command. This is likely caused by Jest autodetecting the number of processes on theĮntire machine ( 36) rather than the number allowed to your container ( 2). log( 'CHILD: url received from parent process', url) Ĭonst browser = await puppeteer.Jest args: -e2e -spec -max-workers=36Īt ChildProcess.spawn (internal/child_process.js:394:11) The code snippet below is a simple example of running parallel downloads with Puppeteer.Ĭonst downloadPath = path. 💡 If you are not familiar with how child process work in Node I highly encourage you to give this article a read. We can combine the child process module with our Puppeteer script and download files in parallel. Child process is how Node.js handles parallel programming. We can fork multiple child_proces in Node. Our CPU cores can run multiple processes at the same time. 💡 Learn more about the single threaded architecture of node here Therefore if we have to download 10 files each 1 gigabyte in size and each requiring about 3 mins to download then with a single process we will have to wait for 10 x 3 = 30 minutes for the task to finish.

It can only execute one process at a time.

You see Node.js in its core is a single-threaded system. However, if you have to download multiple large files things start to get complicated. In this next part, we will dive deep into some of the advanced concepts.

Puppeteer headless download