-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for using sandbox #142
Comments
ignoreAllFlags: true https://github.com/GoogleChrome/chrome-launcher?tab=readme-ov-file#api You can turn it off by adding the defaultFlags here again. However, I cannot turn it off to avoid problems when running with Docker. You can follow the steps I forwarded to turn it off. |
@zfcsoftware losing the default flags just to turn off --no-sandbox may be undesirable. What are the implications here of turning off all flags, seeing that's the only way to turn off --no-sandbox right now. Is it worth to have a param: |
When running with Docker, the browser cannot start if --no-sandbox is not used. I can't remove it for compatibility reasons. I've added the default arguments below. You can add the following arguments to the args value using ignoreAllFlags.
|
fair enough thank you! |
Right now, puppeteer real browser only uses the
--no-sandbox
flag. There should be a setting so we can set the real browser to use sandbox vs--no-sandbox
The text was updated successfully, but these errors were encountered: