-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Bringing back the "no-sandbox" process option #57
Comments
I think we need a general way to opt-out any option like --headless and so on, sounds good to me though for this one in particular. |
FWIW you can enable no-sandbox. This is what I'm using:
|
Thanks @lstanden I think that is exactly what we need! I didn't realize we could configure Cuprite this way! I'm closing the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have had errors when running with a non parametrized user because of the no-sanbox option. Because we do not necessarily want to run with a configured user, I'm trying to get this implemented in the codebase, but I'd like your advise. Would it be good if it was an opt-out parameter in the process constructor?
The text was updated successfully, but these errors were encountered: