Disable AppArmor in CI to allow chrome sandbox#511

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

mafredri merged 1 commit intocoder:masterfromigolaizola:disable-app-armor

Jan 29, 2025

Merged

Disable AppArmor in CI to allow chrome sandbox#511

mafredri merged 1 commit intocoder:masterfromigolaizola:disable-app-armor

Jan 29, 2025

+6 −0

Conversation

Copy link

Contributor

igolaizola commentedJan 29, 2025•
edited by mafredri
Loading

The CI is currently failing with this error when trying to launchTestWasm with wasmbrowsertest:

No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, seehttps://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise seehttps://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

This change disables AppArmor in the CI to allow the sandbox to work.

Fixes#512
Closes#510

Disable AppArmor in CI to allow chrome sandbox

2a82e6e

The CI is currently failing with this error when trying to launch`TestWasm` with wasmbrowsertest:No usable sandbox! If you are running on Ubuntu 23.10+ or another Linuxdistro that has disabled unprivileged user namespaces with AppArmor, seehttps://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md.Otherwise seehttps://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.mdfor more information on developing with the (older) SUID sandbox. If youwant to live dangerously and need an immediate workaround, you can tryusing --no-sandbox.This change disables AppArmor in the CI to allow the sandbox to work.