Missing Chrome installation

Oct 13, 2025 by leolavanderia.com.br 55 views

Introduction

Running Puppeteer with Node.js inside a Docker container can be a challenging task, especially when dealing with dependencies like Chrome. In this article, we will explore the common issues that may arise when trying to run Puppeteer inside a Docker container and provide solutions to overcome these challenges.

Understanding the Issue

When trying to run Puppeteer inside a Docker container, you may encounter the following error message:

Could not find Chrome (ver. 133.0.6943.98). This can occur if either

This error message indicates that Puppeteer is unable to find the Chrome browser, which is a required dependency for running Puppeteer. This can happen for several reasons, including:

Missing Chrome installation: Puppeteer requires Chrome to be installed on the system. If Chrome is not installed, Puppeteer will throw an error.
Incorrect Chrome version: Puppeteer requires a specific version of Chrome to be installed. If the installed version is different, Puppeteer will throw an error.
Docker container configuration: The Docker container configuration may not be set up correctly to allow Puppeteer to access the Chrome browser.

Solutions to Overcome the Issue

1. Install Chrome Inside the Docker Container

One of the simplest solutions to overcome the issue is to install Chrome inside the Docker container. You can do this by adding the following command to your Dockerfile:

RUN apt-get update && apt-get install -y chromium-browser

This command will install the Chromium browser inside the Docker container, which is a compatible alternative to Chrome.

2. Use a Pre-Built Docker Image

Another solution is to use a pre-built Docker image that includes Chrome installed. You can use the node:14-alpine image, which includes Chrome installed:

FROM node:14-alpine

This image is a lightweight version of the Node.js image that includes Chrome installed.

3. Configure the Docker Container

You can also configure the Docker container to allow Puppeteer to access the Chrome browser. You can do this by adding the following command to your Dockerfile:

ENV CHROME_BIN=/usr/bin/chromium-browser

This command will set the CHROME_BIN environment variable to point to the Chromium browser executable.

4. Use a Different Chrome Version

If you are using a specific version of Chrome that is not compatible with Puppeteer, you can try using a different version of Chrome. You can do this by adding the following command to your Dockerfile:

RUN apt-get update && apt-get install -y chromium-browser=133.0.6943.98

This command will install the specific version of Chrome that you require.

5. Use a Different Browser

If you are unable to get Chrome working, you can try using a different browser that is compatible with Puppeteer. You can use the puppeteer-core package, which allows you to use a different browser:

npm install puppeteer-core

This package allows you to use a different browser, such as Firefox or Chromium.

Conclusion

Running Puppeteer with Node.js inside a Docker container can be a challenging task, but there are several solutions that you can use to overcome the issue. By installing Chrome inside the Docker container, using a pre-built Docker image, configuring the Docker container, using a different Chrome version, or using a different browser, you can successfully run Puppeteer inside a Docker container.

Troubleshooting Tips

Check the Docker container logs: If you are experiencing issues with Puppeteer, check the Docker container logs to see if there are any error messages.
Verify the Chrome installation: Make sure that Chrome is installed correctly inside the Docker container.
Check the Chrome version: Verify that the Chrome version is compatible with Puppeteer.
Use a different browser: If you are unable to get Chrome working, try using a different browser that is compatible with Puppeteer.

Example Use Case

Here is an example of how you can use Puppeteer inside a Docker container:

const puppeteer = require('puppeteer');
(async () => 
const browser = await puppeteer.launch({
headless true,
args: ['--no-sandbox', '--disable-setuid-sandbox'],
);
const page = await browser.newPage();
await page.goto('https://example.com');
await page.screenshot( path 'screenshot.png' );
await browser.close();
})();

This code launches a new instance of the Chrome browser inside the Docker container, navigates to the specified URL, takes a screenshot, and then closes the browser.

Conclusion

Q: What is Puppeteer and why do I need it?

A: Puppeteer is a Node.js library developed by the Chrome team that provides a high-level API to control a headless Chrome browser. You need Puppeteer if you want to automate web scraping, web testing, or any other task that requires interacting with a web page.

Q: What is the issue with running Puppeteer inside a Docker container?

A: The issue with running Puppeteer inside a Docker container is that it requires Chrome to be installed on the system. If Chrome is not installed, Puppeteer will throw an error. Additionally, the Docker container configuration may not be set up correctly to allow Puppeteer to access the Chrome browser.

Q: How do I install Chrome inside the Docker container?

A: You can install Chrome inside the Docker container by adding the following command to your Dockerfile:

RUN apt-get update && apt-get install -y chromium-browser

This command will install the Chromium browser inside the Docker container, which is a compatible alternative to Chrome.

Q: What is the difference between Chromium and Chrome?

A: Chromium is an open-source browser developed by Google, while Chrome is a proprietary browser also developed by Google. Chromium is a compatible alternative to Chrome and can be used with Puppeteer.

Q: How do I configure the Docker container to allow Puppeteer to access the Chrome browser?

A: You can configure the Docker container to allow Puppeteer to access the Chrome browser by adding the following command to your Dockerfile:

ENV CHROME_BIN=/usr/bin/chromium-browser

This command will set the CHROME_BIN environment variable to point to the Chromium browser executable.

Q: What if I am using a specific version of Chrome that is not compatible with Puppeteer?

A: If you are using a specific version of Chrome that is not compatible with Puppeteer, you can try using a different version of Chrome. You can do this by adding the following command to your Dockerfile:

RUN apt-get update && apt-get install -y chromium-browser=133.0.6943.98

This command will install the specific version of Chrome that you require.

Q: Can I use a different browser with Puppeteer?

A: Yes, you can use a different browser with Puppeteer. You can use the puppeteer-core package, which allows you to use a different browser:

npm install puppeteer-core

This package allows you to use a different browser, such as Firefox or Chromium.

Q: What are some common issues that I may encounter when running Puppeteer inside a Docker container?

A: Some common issues that you may encounter when running Puppeteer inside a Docker container include:

Missing Chrome installation: Puppeteer requires Chrome to be installed on the system. If Chrome is not installed, Puppeteer will throw an error.
Incorrect Chrome version: Puppeteer requires a specific version of Chrome to be installed. If the installed version is different, Puppeteer will throw an error.
Docker container configuration: The Docker container configuration may not be set up correctly to allow Puppeteer to access the Chrome browser.

Q: How do I troubleshoot issues with Puppeteer inside a Docker container?

A: To troubleshoot issues with Puppeteer inside a Docker container, you can:

Check the Docker container logs: If you are experiencing issues with Puppeteer, check the Docker container logs to see if there are any error messages.
Verify the Chrome installation: Make sure that Chrome is installed correctly inside the Docker container.
Check the Chrome version: Verify that the Chrome version is compatible with Puppeteer.
Use a different browser: If you are unable to get Chrome working, try using a different browser that is compatible with Puppeteer.

Q: What are some best practices for running Puppeteer inside a Docker container?

A: Some best practices for running Puppeteer inside a Docker container include:

Use a pre-built Docker image: Use a pre-built Docker image that includes Chrome installed to simplify the process of setting up the Docker container.
Configure the Docker container: Configure the Docker container to allow Puppeteer to access the Chrome browser.
Use a different browser: Consider using a different browser that is compatible with Puppeteer.
Troubleshoot issues: Troubleshoot issues with Puppeteer inside a Docker container by checking the Docker container logs, verifying the Chrome installation, checking the Chrome version, and using a different browser.