Merged
Conversation
Use the same `--no-sandbox` and `--disable-setuid-sandbox` flags as on GOV.UK Frontend to enable Chrome to run on CI.
Similarly to Karma, Chrome won't launch on CI unless the `--no-sandbox` and `--disable-setuid-sandbox` are set.
✅ Deploy Preview for accessible-autocomplete ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
domoscargin
approved these changes
Dec 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Quick fix for #781 that enables Chrome to run again on CI by using the
--no-sandboxand--disable-sandbox-uuidflags.This was something we used to do on alphagov/govuk-frontend and it gets the tests running again. However, we've since stopped using these flags so we should look at a more long term solution if it exists, as
--no-sandboxis not problematic on CI (each CI run is in a container, which is its own little sandbox), but on our machines we should find a more secure way (although this is mitigated by the fact we only access our dev server)