Cannot run Puppeteer in sandbox mode?

[bantic]

Thanks for this github action, btw! It's been super useful to test a chrome extension!

I was able to get it running, but when puppeteer attempted to launch, it reported this failure:

     Error: Failed to launch chrome!
[70:70:1025/151225.400209:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

I was able to fix this by adding the --no-sandbox arg, but I wondered if it is possible to run in sandbox mode.

According to the sandbox part of the troubleshooting docs, it looks like perhaps the Dockerfile needs to run sudo sysctl -w kernel.unprivileged_userns_clone=1 and then switch into a non-privileged user before it launches the puppeteer browser.

I tried adding the sysctl command to my test script, and it appears that it works, but even so I was still unable to run without the --no-sandbox arg.

[jcblw]

Hmm, so there is a little further down in that document some stuff about using puppeteer in docker. I assume there is some additional steps like USER pptruser which switches to the sandboxed user.

[jcblw]

I would love to support this in the action, I'll take some time today to play around with it

[alexanderdavide]

I experienced the same issue where puppeteer can only launch when --no-sandbox is defined.

The configuration must therefore look like this:

browser = await puppeteer.launch({
      args: ['--no-sandbox'],
      executablePath: process.env.PUPPETEER_EXEC_PATH, // set by docker container
      headless: false,
    });

There does not seem to happen any progress on #18. I suggest to add this missing information in README.md.