Skip to content

CI failing when launching TestWasm with wasmbrowsertest #512

@igolaizola

Description

@igolaizola

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy