


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). Jest args: -e2e -spec -max-workers=36Īt ChildProcess.spawn (internal/child_process.js:394:11)
