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.

Sign up for GitHub

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

Jump to bottom

CI failing when launching TestWasm with wasmbrowsertest #512

Closed
igolaizola opened this issue Jan 29, 2025 · 1 comment · Fixed by #511
Closed

CI failing when launching TestWasm with wasmbrowsertest #512

igolaizola opened this issue Jan 29, 2025 · 1 comment · Fixed by #511

Comments

@igolaizola
Copy link
Contributor

igolaizola commented Jan 29, 2025 •
edited
Loading

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 Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://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.

I have 2 proposals to fix this:

Disable AppArmor

Check this PR: #511

This looks like the way to go. There is an open PR with the same approach here: agnivade/wasmbrowsertest#72

Add --no-sandbox

This requires that this PR is first merged to wasmbrowsertest agnivade/wasmbrowsertest#73
Meanwhile, I have created a PR #510 that points to my fork of wasmbrowsertest to confirm that it works.
@igolaizola
Copy link
Contributor Author

@mafredri PTAL, this should unblock the failing CI

@mafredri mafredri mentioned this issue Jan 29, 2025
Merged
igolaizola added a commit to igolaizola/websocket that referenced this issue Jan 29, 2025
@igolaizola
ci: disable AppArmor on daily and static workflows
ab446bc 
AppArmor was disabled in CI workflows, but it was not disabled in the
daily and static workflows.

References coder#512
@igolaizola igolaizola mentioned this issue Jan 29, 2025
Merged
igolaizola added a commit to igolaizola/websocket that referenced this issue Jan 29, 2025
@igolaizola
ci: disable AppArmor on daily and static workflows
38b4c4c 
AppArmor was disabled in CI workflows, but it was not disabled in the
daily and static workflows.

References coder#512
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Disable AppArmor in CI to allow chrome sandbox igolaizola/websocket
1 participant
@igolaizola