ci: use aa-exec to fix Puppeteer on Ubuntu 24.04 CI
#825
Conversation
This file contains 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
Ubuntu 24.04 has stricter AppArmor policies that prevent Puppeteer from running, with an error like: > Failed to launch the browser process! > [0109/235031.343250:FATAL:zygote_host_impl_linux.cc(128)] 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. We can use [`aa-exec`][1] to explicitly set the `chrome` policy and get it working again. [1]: https://manpages.ubuntu.com/manpages/noble/man1/aa-exec.1.html See: mermaid-js#730 (comment)
aloisklink
force-pushed
the
test/fix-mermaid-cli-on-ubuntu-24.04
branch
from
81a4faa to
acbf2c9
Compare
aloisklink
added a commit
to aloisklink/remark-mermaid-dataurl
that referenced
this pull request
Jan 10, 2025
Use `aa-exec --profile=chrome` to run our tests and therefore Puppeteer with the `chrome` security profile. This allows chrome to run with the same permissions as it had on Ubuntu 22.04, which is required. See: mermaid-js/mermaid-cli#825
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📑 Summary
Ubuntu 24.04 has stricter AppArmor policies that prevent Puppeteer from running, with an error like:
We can use
aa-execto explicitly set thechromepolicy and get it working again.See: #730 (comment)
See: actions/runner-images#10015
See: puppeteer/puppeteer#12818
📏 Design Decisions
I've used
aa-execsince it's seems the easiest way to set the config, and it still means that Puppeteer uses most of it's sandbox features.📋 Tasks
Make sure you
masterbranch