Skip to content
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

Closed
niezbop opened this issue Feb 5, 2019 · 4 comments
Closed

Bringing back the "no-sandbox" process option #57

niezbop opened this issue Feb 5, 2019 · 4 comments

Comments

@niezbop
Copy link
Contributor

niezbop commented Feb 5, 2019

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?

@route
Copy link
Member

route commented Feb 5, 2019

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.

@lstanden
Copy link

lstanden commented Feb 7, 2019

FWIW you can enable no-sandbox. This is what I'm using:

Capybara.register_driver :cuprite do |app|
  Capybara::Cuprite::Driver.new(
    app,
    js_errors: true,
    headless: true,
    window_size: [1366, 768], # most popular window size (35%)
    browser_options: {
      'no-sandbox': nil
    }
  )
end

@lacostej
Copy link
Contributor

lacostej commented Feb 8, 2019

@lstanden good to know! @niezbop maybe we just want to document this instead of adding more code.

@niezbop
Copy link
Contributor Author

niezbop commented Feb 8, 2019

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

@niezbop niezbop closed this as completed Feb 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants