0.15.1 does not work with Debian Trixie on ARM
Author: sdavidsCreated Mar 7, 2026Updated Mar 7, 2026
Describe the bug
@lhci/[email protected] does not work with Debian Trixie on ARM.
Possibly, it does not work on any ARM-Linux with chromium/chromium-sandbox.
To Reproduce
$ mkdir -p /tmp/lhci-test && cd "$_"
$ cat <<'EOF' >Dockerfile
FROM debian:13.3
RUN export DEBIAN_FRONTEND=noninteractive \
&& apt-get update \
&& apt-get --yes install \
chromium \
chromium-sandbox \
nodejs \
npm
WORKDIR /test
RUN npm init -y \
&& npm i -D @lhci/[email protected]
RUN mkdir dist && \
printf '<!doctype html><title>Test</title><h1>Test</h1>' >dist/index.html
RUN chown www-data:www-data -R /test
USER www-data
CMD ["npx", "lhci", "autorun"]
EOF
$ docker build --platform linux/arm64 --tag lhci:latest .
$ docker run --platform linux/arm64 --init --rm lhci:latest
✅ .lighthouseci/ directory writable
⚠️ Configuration file not found
✅ Chrome installation found
Healthcheck passed!
Automatically determined ./dist as `staticDistDir`.
Set it explicitly in lighthouserc.json if incorrect.
Started a web server on port 36351...
Running Lighthouse 3 time(s) on http://localhost:36351/index.html
Run #1...failed!
Error: Lighthouse failed with exit code 1
at ChildProcess.<anonymous> (/test/node_modules/@lhci/cli/src/collect/node-runner.js:120:21)
at ChildProcess.emit (node:events:524:28)
at ChildProcess._handle.onexit (node:internal/child_process:293:12)
2026-03-07T18:05:11.777Z LH:ChromeLauncher Waiting for browser.
2026-03-07T18:05:11.777Z LH:ChromeLauncher Waiting for browser...
2026-03-07T18:05:12.287Z LH:ChromeLauncher Waiting for browser.....
2026-03-07T18:05:12.796Z LH:ChromeLauncher Waiting for browser.......
2026-03-07T18:05:13.304Z LH:ChromeLauncher Waiting for browser.........
2026-03-07T18:05:13.808Z LH:ChromeLauncher Waiting for browser...........
2026-03-07T18:05:14.315Z LH:ChromeLauncher Waiting for browser.............
2026-03-07T18:05:14.820Z LH:ChromeLauncher Waiting for browser...............
2026-03-07T18:05:15.324Z LH:ChromeLauncher Waiting for browser.................
2026-03-07T18:05:15.827Z LH:ChromeLauncher Waiting for browser...................
2026-03-07T18:05:16.332Z LH:ChromeLauncher Waiting for browser.....................
2026-03-07T18:05:16.838Z LH:ChromeLauncher Waiting for browser.......................
2026-03-07T18:05:17.350Z LH:ChromeLauncher Waiting for browser.........................
2026-03-07T18:05:17.855Z LH:ChromeLauncher Waiting for browser...........................
2026-03-07T18:05:18.360Z LH:ChromeLauncher Waiting for browser.............................
2026-03-07T18:05:18.904Z LH:ChromeLauncher Waiting for browser...............................
2026-03-07T18:05:19.418Z LH:ChromeLauncher Waiting for browser.................................
2026-03-07T18:05:19.921Z LH:ChromeLauncher Waiting for browser...................................
2026-03-07T18:05:20.424Z LH:ChromeLauncher Waiting for browser.....................................
2026-03-07T18:05:20.930Z LH:ChromeLauncher Waiting for browser.......................................
2026-03-07T18:05:21.435Z LH:ChromeLauncher Waiting for browser.........................................
2026-03-07T18:05:21.942Z LH:ChromeLauncher Waiting for browser...........................................
2026-03-07T18:05:22.447Z LH:ChromeLauncher Waiting for browser.............................................
2026-03-07T18:05:22.959Z LH:ChromeLauncher Waiting for browser...............................................
2026-03-07T18:05:23.466Z LH:ChromeLauncher Waiting for browser.................................................
2026-03-07T18:05:23.970Z LH:ChromeLauncher Waiting for browser...................................................
2026-03-07T18:05:24.480Z LH:ChromeLauncher Waiting for browser.....................................................
2026-03-07T18:05:24.989Z LH:ChromeLauncher Waiting for browser.......................................................
2026-03-07T18:05:25.494Z LH:ChromeLauncher Waiting for browser.........................................................
2026-03-07T18:05:26.001Z LH:ChromeLauncher Waiting for browser...........................................................
2026-03-07T18:05:26.510Z LH:ChromeLauncher Waiting for browser.............................................................
2026-03-07T18:05:27.014Z LH:ChromeLauncher Waiting for browser...............................................................
2026-03-07T18:05:27.523Z LH:ChromeLauncher Waiting for browser.................................................................
2026-03-07T18:05:28.029Z LH:ChromeLauncher Waiting for browser...................................................................
2026-03-07T18:05:28.533Z LH:ChromeLauncher Waiting for browser.....................................................................
2026-03-07T18:05:29.042Z LH:ChromeLauncher Waiting for browser.......................................................................
2026-03-07T18:05:29.549Z LH:ChromeLauncher Waiting for browser.........................................................................
2026-03-07T18:05:30.057Z LH:ChromeLauncher Waiting for browser...........................................................................
2026-03-07T18:05:30.563Z LH:ChromeLauncher Waiting for browser.............................................................................
2026-03-07T18:05:31.069Z LH:ChromeLauncher Waiting for browser...............................................................................
2026-03-07T18:05:31.574Z LH:ChromeLauncher Waiting for browser.................................................................................
2026-03-07T18:05:32.079Z LH:ChromeLauncher Waiting for browser...................................................................................
2026-03-07T18:05:32.587Z LH:ChromeLauncher Waiting for browser.....................................................................................
2026-03-07T18:05:33.094Z LH:ChromeLauncher Waiting for browser.......................................................................................
2026-03-07T18:05:33.602Z LH:ChromeLauncher Waiting for browser.........................................................................................
2026-03-07T18:05:34.110Z LH:ChromeLauncher Waiting for browser...........................................................................................
2026-03-07T18:05:34.617Z LH:ChromeLauncher Waiting for browser.............................................................................................
2026-03-07T18:05:35.119Z LH:ChromeLauncher Waiting for browser...............................................................................................
2026-03-07T18:05:35.624Z LH:ChromeLauncher Waiting for browser.................................................................................................
2026-03-07T18:05:36.131Z LH:ChromeLauncher Waiting for browser...................................................................................................
2026-03-07T18:05:36.637Z LH:ChromeLauncher Waiting for browser.....................................................................................................
2026-03-07T18:05:37.141Z LH:ChromeLauncher Waiting for browser.......................................................................................................
2026-03-07T18:05:37.147Z LH:ChromeLauncher:error connect ECONNREFUSED 127.0.0.1:38119
2026-03-07T18:05:37.149Z LH:ChromeLauncher:error Logging contents of /tmp/lighthouse.wJzYJuj/chrome-err.log
2026-03-07T18:05:37.149Z LH:ChromeLauncher:error [75:75:0307/180511.860571:ERROR:third_party/crashpad/crashpad/util/file/filesystem_posix.cc:63] mkdir : No such file or directory (2)
[75:75:0307/180511.861892:ERROR:content/browser/zygote_host/zygote_host_impl_linux.cc:128] No usable sandbox! If this is a Debian system, please install the chromium-sandbox package to solve this problem. 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. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
chrome_crashpad_handler: --database is required
Try 'chrome_crashpad_handler --help' for more information.
Unable to connect to ChromeExpected behavior It works.
Logs/Screenshots
[75:75:0307/180511.861892:ERROR:content/browser/zygote_host/zygote_host_impl_linux.cc:128] No usable sandbox! If this is a Debian system, please install the chromium-sandbox package to solve this problem. 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. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
chrome_crashpad_handler: --database is requiredEnvironment (please complete the following information):
- OS: Linux 00bc40283ecb 6.12.72-linuxkit #1 SMP Mon Feb 16 11:19:07 UTC 2026 aarch64 GNU/Linux
- Browser Chromium 145.0.7632.159 built on Debian GNU/Linux 13 (trixie)
- Version 0.15.1
Additional context
$ docker run --platform linux/arm64 --init --rm -it lhci:latest sh
$ apt list chromium
chromium/stable-security,now 145.0.7632.159-1~deb13u1 arm64 [installed]
Notice: There is 1 additional version. Please use the '-a' switch to see it
$ apt list chromium-sandbox
chromium-sandbox/stable-security,now 145.0.7632.159-1~deb13u1 arm64 [installed]
Notice: There is 1 additional version. Please use the '-a' switch to see itSource: GoogleChrome/lighthouse-ci