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.

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

Add WASM_NO_SANDBOX=on to disable Chrome sandbox #510

Closed
wants to merge 1 commit into from

Conversation

igolaizola
Copy link
Contributor

The CI is currently failing with the following error message: "No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces..."

This commit updates the wasmbrowsertest to a version that supports the WASM_NO_SANDBOX environment variable, which disables the Chrome sandbox. Then it adds the environment variable to TestWasm in conn_test.go.

The CI is currently failing with the following error message:
"No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux
distro that has disabled unprivileged user namespaces..."

This commit updates the wasmbrowsertest to a version that supports the
WASM_NO_SANDBOX environment variable, which disables the Chrome sandbox.
Then it adds the environment variable to `TestWasm` in `conn_test.go`.
@igolaizola igolaizola marked this pull request as draft January 29, 2025 08:09
@igolaizola
Copy link
Contributor Author

Moving this to draft because it is pointing to my own fork of wasmbrowsertest.
I have opened a PR that adds WASM_NO_SANDBOX to wasmbrowsertest: agnivade/wasmbrowsertest#73

However, this other PR could be a better fix for this same problem: #511

@igolaizola
Copy link
Contributor Author

Closing this, as this problem will be fixed with #511

@igolaizola igolaizola closed this Jan 29, 2025
@igolaizola igolaizola deleted the fix-ci-wasm-test branch January 29, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant