If you try to install a different version of Puppeteer into this image, you may run into compatibility issues, because the Chromium version bundled with puppeteer will not match the version of Chromium that's pre-installed. For example, apify/actor-node-puppeteer-chrome:16-13.7.0 comes with Node.js 16 and Puppeteer v13.7.0. Images that include a pre-installed automation library, which means all images that include puppeteer or playwright in their name, are also tagged with the pre-installed version of the library. To select the preferred version, use the appropriate number as the image tag. Currently, Node.js versions 16 and 18 are supported (legacy versions still exist, see DockerHub). Our images are built with multiple Node.js versions to ensure backwards compatibility. It will ensure that a future update of Node.js will not break our automations. We recommend always using at least the Node.js version tag in production Dockerfiles. If you use the image name without a version tag, you'll always get the latest available version.
One for Node.js version and second for pre-installed web automation library version. Here's a full list of our Docker images.Įach image is tagged with up to 2 version tags, depending on the type of the image. Overview īrowsers are pretty big, so we try to provide a wide variety of images to suit the specific needs. We use them every day on the Apify Platform.Īll images can be found in their GitHub repo and in our DockerHub. But there's no need to worry about that, because we already created base images that you can freely use. Running headless browsers in Docker requires a lot of setup to do it right.
0 kommentar(er)
