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.

Sign up for GitHub

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

Jump to bottom

Point out need for --no-sandbox with headless chrome #878

Closed
jason0x43 opened this issue Feb 7, 2018 · 0 comments
Closed

Point out need for --no-sandbox with headless chrome #878

jason0x43 opened this issue Feb 7, 2018 · 0 comments
Labels
domain-documentation Related to Intern's documentation

Comments

@jason0x43
Copy link
Member

When running headless Chrome in a container without a defined user, the chromeOptions environment property needs a --no-sandbox arg (in addition to the other headless args), or Chrome won't be able to startup. We should mention this in the "how to run headless chrome" section.

See https://developers.google.com/web/updates/2017/04/headless-chrome
@jason0x43 jason0x43 added the domain-documentation Related to Intern's documentation label Feb 7, 2018
@dcramer dcramer mentioned this issue Mar 19, 2019
Merged
@mikestead mikestead mentioned this issue May 5, 2019
Merged
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
528cd1f 
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
433197d 
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
810c388 
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
02013ff 
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
b04971b 
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
e44d84c 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
dcb9c2a 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
fe350db 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 17, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
6804868 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
tahb added a commit to dxw/transition that referenced this issue Sep 18, 2019
@tahb
(fix) Tests can be run without any dependency on the host machine
46378b6 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
@notdanilo notdanilo mentioned this issue Feb 7, 2020
Closed
3 tasks
Floppy pushed a commit to dxw/transition that referenced this issue Feb 14, 2020
@tahb @Floppy
(fix) Tests can be run without any dependency on the host machine
210ebc2 
* Use Docker for every part of running the test suite to ensure consistent passing.
* This was causing failures where CI didn't have the appropriate tooling installed. These included chrome, chromedriver.
* In order to debug and fix this I removed the govuk_test gem and included the simple configuration. 2 small amendments were required to fix a problem in using selenium with Docker theintern/intern#878. Given the test gem aims to provide consistency across the GDS stack we aren't losing any value in removing it as an abstraction for how to configure our test suite.
@themarcelor themarcelor mentioned this issue Jun 17, 2020
Merged
jason0x43 added a commit to jason0x43/intern that referenced this issue Jul 7, 2020
@jason0x43
Add note about --no-sandbox for headless chrome
99c2bfa 
resolves theintern#878

[ci skip]
jason0x43 added a commit to jason0x43/intern that referenced this issue Jul 13, 2020
@jason0x43
Add note about --no-sandbox for headless chrome
f9ec0ba 
resolves theintern#878

[ci skip]
jason0x43 added a commit that referenced this issue Jul 21, 2020
@jason0x43
Add note about --no-sandbox for headless chrome
3d16ae8 
resolves #878

[ci skip]
jason0x43 added a commit that referenced this issue Aug 10, 2020
@jason0x43
Add note about --no-sandbox for headless chrome
b43dc9c 
resolves #878

[ci skip]
This was referenced Sep 15, 2020
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain-documentation Related to Intern's documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jason0x43