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.

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

ci: disable AppArmor restrictions on Ubuntu and update troubleshooting.md #13196

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

OrKoN
Copy link
Collaborator

@OrKoN OrKoN commented Oct 16, 2024

See #12818

@OrKoN OrKoN force-pushed the orkon/ubuntu-test branch 3 times, most recently from 6c5765d to 49870c4 Compare October 16, 2024 07:58
@OrKoN OrKoN changed the title test: test ubuntu-24.04 ci: disable AppArmor restrictions on Ubuntu and update troubleshooting.md Oct 16, 2024
@OrKoN OrKoN force-pushed the orkon/ubuntu-test branch from 49870c4 to d752998 Compare October 16, 2024 08:29
@OrKoN OrKoN added the full-ci label Oct 16, 2024
@OrKoN OrKoN marked this pull request as ready for review October 16, 2024 08:38
@OrKoN OrKoN force-pushed the orkon/ubuntu-test branch from d752998 to ca0e1c9 Compare October 16, 2024 10:39
@OrKoN OrKoN force-pushed the orkon/ubuntu-test branch from ca0e1c9 to 88ef09c Compare October 16, 2024 10:59
@OrKoN OrKoN merged commit 3984449 into main Oct 16, 2024
82 checks passed
@OrKoN OrKoN deleted the orkon/ubuntu-test branch October 16, 2024 12:13
smaye81 added a commit to connectrpc/conformance that referenced this pull request Oct 24, 2024
From Puppeteer docs:

> Ubuntu 23.10+ (or possibly other Linux distros in the future) ship an
AppArmor profile that applies to Chrome stable binaries installed at
/opt/google/chrome/chrome (the default installation path). This policy
is stored at /etc/apparmor.d/chrome. This AppArmor policy prevents
Chrome for Testing binaries downloaded by Puppeteer from using user
namespaces resulting in the `No usable sandbox!` error when trying to
launch the browser

We are currently seeing this error in CI due to our usage of
`ubuntu-latest` in our CI Github Action images. It seems that Puppeteer
has disabled this check as part of
puppeteer/puppeteer#13196, but it doesn't look
like this has been released yet. Once it has, we could potentially
update to that latest version of Puppeteer and reinstate usage of
`ubuntu-latest`. In the meantime, though, this pins our CI image to
`ubuntu-22.04` to get CI to pass.

---------

Signed-off-by: Steve Ayers <[email protected]>
ahuigo added a commit to ahuigo/astral that referenced this pull request Jan 7, 2025
ahuigo added a commit to ahuigo/astral that referenced this pull request Jan 7, 2025
ahuigo added a commit to ahuigo/astral that referenced this pull request Jan 7, 2025
lino-levan pushed a commit to lino-levan/astral that referenced this pull request Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants