From 17634e9f2ac2849b5916f8ece6d3400372ed93c1 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Mon, 12 Feb 2024 23:47:30 +0100 Subject: [PATCH] docs: update sandbox path (#11905) --- docs/troubleshooting.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index fe508bd1f97..73e333fd2c3 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -221,13 +221,13 @@ sudo sysctl -w kernel.unprivileged_userns_clone=1 ### [alternative] Setup [setuid sandbox](https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/suid_sandbox_development.md) The setuid sandbox comes as a standalone executable and is located next to the -Chromium that Puppeteer downloads. It is fine to re-use the same sandbox -executable for different Chromium versions, so the following could be done only +Chrome that Puppeteer downloads. It is fine to re-use the same sandbox +executable for different Chrome versions, so the following could be done only once per host environment: ```bash -# cd to the downloaded instance -cd /node_modules/puppeteer/.local-chromium/linux-/chrome-linux/ +# cd to Puppeteer cache directory (adjust the path if using a different cache directory). +cd ~/.cache/puppeteer/chrome/linux-/chrome-linux64/ sudo chown root:root chrome_sandbox sudo chmod 4755 chrome_sandbox # copy sandbox executable to a shared location @@ -243,6 +243,12 @@ this case, add the following to the `~/.bashrc` or `.zshenv`: export CHROME_DEVEL_SANDBOX=/usr/local/sbin/chrome-devel-sandbox ``` +or to your `Dockerfile`: + +``` +ENV CHROME_DEVEL_SANDBOX /usr/local/sbin/chrome-devel-sandbox +``` + ## Running Puppeteer on Travis CI > 👋 We ran our tests for Puppeteer on Travis CI until v6.0.0 (when we've