Forge - Ubuntu 22 vs 24 & AppArmor #900
Unanswered
RyanGSampson
asked this question in
Q&A
Replies: 1 comment
-
The following profile is working for me on Forge with Ubuntu 24.04. Browsershot and its dependencies were installed per the documentation. Create AppArmor profile and reload: export CHROMIUM_BUILD_PATH=/@{HOME}/.cache/puppeteer/**/chrome
cat | sudo tee /etc/apparmor.d/chrome-puppeteer <<EOF
abi <abi/4.0>,
include <tunables/global>
profile chrome $CHROMIUM_BUILD_PATH flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists <local/chrome>
}
EOF
sudo service apparmor reload # reload AppArmor profiles to include the new one |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All,
I use Forge to deploy my laravel application.
My production server is running on Ubuntu 22 w/ Browsershot performing perfectly.
I recently provisioned a new dev server using Ubunti 24 and ran into the issue of AppArmor not allowing Puppeteer to spin up Chromim in a sandbox.
Disabling sandboxing is not something that I am willing to do.
For now, going back to Ubuntu 22 is my solution.
Wonding if anyone has experience in bypassing AppArmor in 24?
I tried the below to no avail.
Thanks for reading.
sudo nano /etc/apparmor.d/local/usr.local.bin.chromium
profile chromium /snap/bin/chromium flags=(unconfined) {
userns,
include if exists <local/chromium>
}
sudo apparmor_parser -r /etc/apparmor.d/usr.local.bin.chromium
Beta Was this translation helpful? Give feedback.
All reactions