From 58d5f9c3ae1233cb1ebbce88d9b20a9fe0953e4f Mon Sep 17 00:00:00 2001 From: David Barton <43063460+theDavidBarton@users.noreply.github.com> Date: Tue, 9 Feb 2021 09:45:36 +0100 Subject: [PATCH] docs(troubleshooting): update broken Dockerfile link to historical one (#6828) Co-authored-by: Mathias Bynens --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 3199c8e6922..71bcfb3546a 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -247,7 +247,7 @@ Running Puppeteer smoothly on CircleCI requires the following steps: ## Running Puppeteer in Docker -> 👋 We use [Cirrus Ci](https://cirrus-ci.org/) to run our tests for Puppeteer in a Docker container - see our [`Dockerfile.linux`](https://github.com/puppeteer/puppeteer/blob/main/.ci/node10/Dockerfile.linux) for reference. +> 👋 We used [Cirrus Ci](https://cirrus-ci.org/) to run our tests for Puppeteer in a Docker container until v3.0.x - see our historical [`Dockerfile.linux` (v3.0.1)](https://github.com/puppeteer/puppeteer/blob/v3.0.1/.ci/node12/Dockerfile.linux) for reference. Getting headless Chrome up and running in Docker can be tricky. The bundled Chromium that Puppeteer installs is missing the necessary