fix(unlighthouse): launch Chrome with --no-sandbox in CI - #114
Merged
Merged
Conversation
GitHub's ubuntu-24.04 runners disable unprivileged user namespaces, so Chrome aborts with 'No usable sandbox!' and the unlighthouse runner fails on every CI run (it had never run on a runner before sites adopted single-environment). On Linux with CI set, point CHROME_PATH and PUPPETEER_EXECUTABLE_PATH at a wrapper that adds --no-sandbox. Opt out with VOIDFLOW_CHROME_SANDBOX=1. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Owner
Author
|
Validated on a real GitHub runner via soundry#79 (temporarily pointing the lighthouse script at this branch): the log shows |
taraxvoid
pushed a commit
that referenced
this pull request
Oct 2, 2026
🤖 I have created a release *beep* *boop* --- ## [0.11.1](v0.11.0...v0.11.1) (2026-10-02) ### Bug Fixes * **unlighthouse:** launch Chrome with --no-sandbox in CI ([#114](#114)) ([67daebb](67daebb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
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
1 participant
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.
With
single-environment: true, soundry and synthomaha now runtest:e2e:lighthouseonmain, and the runner fails on GitHub runners:FATAL: zygote_host_impl_linux.cc: No usable sandbox! ... Ubuntu 23.10+ ... AppArmor disabled unprivileged user namespaces. The runner had never executed on a runner before (it only ran on PRs intolive, which these sites never open).On Linux with
CIset, the runner now pointsCHROME_PATH/PUPPETEER_EXECUTABLE_PATHat a small wrapper script that execs Chrome with--no-sandbox. Callers change nothing; it only applies in CI, where the browser loads our own static build. Opt out withVOIDFLOW_CHROME_SANDBOX=1.Unit tests cover the wrapper (executable, argument order, paths with spaces/quotes). Validating on a real runner via a caller PR next; will report the result here.
🤖 Generated with Claude Code