Closed dbro closed 3 years ago
Following up: this seems to have been the problem that was causing pyppeteer to fail: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#setting-up-chrome-linux-sandbox
so in my case instead of disabling the Chromium sandbox, I could run this command first: sudo sysctl -w kernel.unprivileged_userns_clone=1
This is on Debian runing kernel version 4.19
@dbro You may want to take a look at the webchanges fork, which was suggested by the author to optimize it for HTML; it has quite a few improvements specific to Pyppetter-run jobs (including, if you need it for your setup, the optional directive switches
for Chromium that allows you to pass on any switch you want).
See a list of improvements here and examples using switches starting here.
Thanks. I will close this pull request.
I was getting errors when running a browser job which were fixed by adding the "--no-sandbox" option for Chromium. This pull requests adds support for this option in the yaml browser job definition.
This was mentioned in an early message as part of the discuss for issue #555 but I don't know if it is still relevant.