Skip to content

Commit dba56d5

Browse files
authored
Pin to Ubuntu 22.04 to fix Puppeteer (#940)
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]>
1 parent 80c1569 commit dba56d5

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

.github/workflows/ci.yaml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,10 @@ permissions:
99
contents: read
1010
jobs:
1111
ci:
12-
runs-on: ubuntu-latest
12+
# TODO(sayers) - Need to run on 22.04 for the time being until
13+
# https://github.com/puppeteer/puppeteer/pull/13196 is released
14+
# See https://github.com/connectrpc/conformance/pull/940 for context
15+
runs-on: ubuntu-22.04
1316
strategy:
1417
matrix:
1518
# When changing this, don't forget to also update

0 commit comments

Comments
 (0)