hai/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-21 20:28:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: add --no-sandbox for Chromium in CI/container environments

Browse Source 
Chromium's sandbox requires unprivileged user namespaces which are
disabled in Docker containers. Without --no-sandbox, Chromium silently
fails to launch, causing browse E2E tests to exhaust all turns trying
to start the server.

Detects CI or CONTAINER env vars and adds --no-sandbox automatically.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-23 16:50:19 -07:00
parent eb4e20c6c4
commit 4ba89d4f49
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
browse/src/browser-manager.ts
View File

@@ -69,6 +69,13 @@ export class BrowserManager {
const launchArgs: string[] = []; const launchArgs: string[] = [];
let useHeadless = true; let useHeadless = true;
// Docker/CI: Chromium sandbox requires unprivileged user namespaces which
// are typically disabled in containers. Detect container environment and
// add --no-sandbox automatically.
if (process.env.CI || process.env.CONTAINER) {
launchArgs.push('--no-sandbox');
}
if (extensionsDir) { if (extensionsDir) {
launchArgs.push( launchArgs.push(
`--disable-extensions-except=${extensionsDir}`, `--disable-extensions-except=${extensionsDir}`,