Add WASM_NO_SANDBOX env to disable Chrome sandbox#73
Closed
igolaizola wants to merge 1 commit intoagnivade:masterfrom
Closed
Add WASM_NO_SANDBOX env to disable Chrome sandbox#73igolaizola wants to merge 1 commit intoagnivade:masterfrom
igolaizola wants to merge 1 commit intoagnivade:masterfrom
Conversation
On GitHub Actions (and similar CI environments), Chrome often fails to launch due to its sandbox being unavailable, resulting in the error: "No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces..." This commit adds support for a new environment variable, `WASM_NO_SANDBOX`, which, when set to "on", appends `chromedp.NoSandbox` to the Chrome options. This allows Chrome to run without a sandbox and avoids the crash in CI pipelines that lack the necessary permissions or configurations for the standard Chrome sandbox.
This was referenced Jan 29, 2025
Author
|
We finally fixed our issues by disabling AppArmor in the CI, same as proposed in this PR: #72 |
Owner
|
In that case, I guess this PR is no longer needed? |
Author
Perhaps there are other use cases where |
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.
On GitHub Actions (and similar CI environments), Chrome often fails to launch due to its sandbox being unavailable, resulting in the error: "No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces..."
This commit adds support for a new environment variable,
WASM_NO_SANDBOX, which, when set to "on", appendschromedp.NoSandboxto the Chrome options. This allows Chrome to run without a sandbox and avoids the crash in CI pipelines that lack the necessary permissions or configurations for the standard Chrome sandbox.