Error: Failed to launch chrome! spawn /app/node_modules/puppeteer/.local-chromium/linux-609904/chrome-linux/chrome ENOENT

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.11.0
• Platform / OS version: MAC 10.14.3
• URLs (if applicable):
• Node.js version: v8.9.4

I have been trying to get my Node application, using Puppeteer as the testing framework to run via docker. It works perfectly well when running locally on my. However when running via container I keep running into the same issue.

I have tried almost every boiler-plate Dockerfile I have seen from other users online but none of them can address the issue Im seeing.

Error: Failed to launch chrome! spawn /app/node_modules/puppeteer/.local-chromium/linux-609904/chrome-linux/chrome ENOENT

When I see other people with this issue they all seem to show different linux versions and not the specific one I am seeing after download: linux-609904. What is the best way to audit whats wrong with this version?

[ben-turner]

@arapocket Thanks for commenting—I forgot to follow up after I found a solution. It’s been a couple of weeks so I don’t remember exactly which change fixed it, but here’s the configuration I’m running:

In my Dockerfile I have

RUN apk add --nocache udev ttf-freefont chromium git
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true
ENV CHROMIUM_PATH /usr/bin/chromium-browser

// npm install, etc.

And then to launch the browser

puppeteer.launch({
  executablePath: process.env.CHROMIUM_PATH,
  args: ['--no-sandbox'], // This was important. Can't remember why
});

I also locked puppeteer to 1.17.0 in my package.json. I think that was to make the chromium and puppeteer versions match.

[ben-turner]

I’m running puppeteer on node:12-alpine. After building the container, I’ve been shelling into it with docker run -ti [container] /bin/sh. I can then see that there is indeed a binary at /home/node/node_modules/puppeteer/.local-chromium/linux-674921/chrome-linux/chrome, but if I try to run it, I get the error /bin/sh: ./chrome: not found, which matches up with the ENOENT error that I get from puppeteer. I’ll follow up here if I find a solution, but I just wanted to point out that it might not be a failed download in case anyone else comes across this.