Executing lighthouse lic gets stuck in alpine nodejs environment #15793

ZengTianShengZ · 2024-02-01T03:07:19Z

FAQ

Yes, my issue is not about variability or throttling.
Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

What happened?

When I execute Lighthouse in the alpine nodejs docker environment, Lighthouse gets stuck. I see in the log that chromium-browser is started normally, but Lighthouse keeps getting stuck and cannot be executed.

 sudo lighthouse  --verbose https://baidu.com  --enable-error-reporting --chrome-flags="--no-sandbox --headless --disable-gpu" --output=json
  LH:ChromeLauncher:verbose created /tmp/lighthouse.A0a1Iw4 +0ms
  LH:ChromeLauncher:verbose Launching with command:
  LH:ChromeLauncher:verbose "/usr/bin/chromium-browser" --disable-features=Translate,OptimizationHints,MediaRouter,DialMediaRouteProvider,CalculateNativeWinOcclusion,InterestFeedContentSuggestions,CertificateTransparencyComponentUpdater,AutofillServerCommunication --disable-extensions --disable-component-extensions-with-background-pages --disable-background-networking --disable-component-update --disable-client-side-phishing-detection --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-default-browser-check --no-first-run --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-timer-throttling --disable-ipc-flooding-protection --password-store=basic --use-mock-keychain --force-fieldtrials=*BackgroundTracing/default/ --disable-hang-monitor --disable-prompt-on-repost --disable-domain-reliability --remote-debugging-port=39804 --disable-setuid-sandbox --user-data-dir=/tmp/lighthouse.A0a1Iw4 --no-sandbox --headless --disable-gpu about:blank +5ms
  LH:ChromeLauncher:verbose Chrome running with pid 539 on port 39804. +7ms
  LH:ChromeLauncher Waiting for browser. +1ms
  LH:ChromeLauncher Waiting for browser... +0ms
  LH:ChromeLauncher Waiting for browser..... +506ms
  LH:ChromeLauncher Waiting for browser.....✓ +2ms
  LH:status:verbose Initialize config +1ms
  LH:status:verbose Resolve artifact definitions +3ms
  LH:statusEnd:verbose Resolve artifact definitions +102ms
  LH:statusEnd:verbose Initialize config +834ms
  LH:status:verbose Gather phase +0ms

What did you expect?

Lighthouse can execute normally and output results in alpine nodejs docker environment

What have you tried?

No response

How were you running Lighthouse?

CLI, node

Lighthouse Version

11.5.0

Chrome Version

Chromium 112.0.5615.165

Node Version

v18.15.0

OS

Linux

Relevant log output

Specify --help for available options
lighthouse-service-app-d84d67d8f-8r6zm:/app# lighthouse  --version     
11.5.0
lighthouse-service-app-d84d67d8f-8r6zm:/app# node -v
v18.15.0
lighthouse-service-app-d84d67d8f-8r6zm:/app# chromium-browser
[749:749:0201/110558.351580:ERROR:zygote_host_impl_linux.cc(100)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
lighthouse-service-app-d84d67d8f-8r6zm:/app# chromium-browser --version
Chromium 112.0.5615.165 
lighthouse-service-app-d84d67d8f-8r6zm:/app#  sudo lighthouse  --verbose https://baidu.com  --enable-error-reporting --chrome-flags="--no-sandbox --headless --disable-gpu" --output=json
  LH:ChromeLauncher:verbose created /tmp/lighthouse.xpmKgXW +0ms
  LH:ChromeLauncher:verbose Launching with command:
  LH:ChromeLauncher:verbose "/usr/bin/chromium-browser" --disable-features=Translate,OptimizationHints,MediaRouter,DialMediaRouteProvider,CalculateNativeWinOcclusion,InterestFeedContentSuggestions,CertificateTransparencyComponentUpdater,AutofillServerCommunication --disable-extensions --disable-component-extensions-with-background-pages --disable-background-networking --disable-component-update --disable-client-side-phishing-detection --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-default-browser-check --no-first-run --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-timer-throttling --disable-ipc-flooding-protection --password-store=basic --use-mock-keychain --force-fieldtrials=*BackgroundTracing/default/ --disable-hang-monitor --disable-prompt-on-repost --disable-domain-reliability --remote-debugging-port=35116 --disable-setuid-sandbox --user-data-dir=/tmp/lighthouse.xpmKgXW --no-sandbox --headless --disable-gpu about:blank +11ms
  LH:ChromeLauncher:verbose Chrome running with pid 782 on port 35116. +7ms
  LH:ChromeLauncher Waiting for browser. +1ms
  LH:ChromeLauncher Waiting for browser... +0ms
  LH:ChromeLauncher Waiting for browser..... +506ms
  LH:ChromeLauncher Waiting for browser.....✓ +2ms
  LH:status:verbose Initialize config +1ms
  LH:status:verbose Resolve artifact definitions +2ms
  LH:statusEnd:verbose Resolve artifact definitions +100ms
  LH:statusEnd:verbose Initialize config +792ms
  LH:status:verbose Gather phase +1ms

adamraine · 2024-02-02T21:39:26Z

Does adding --disable-dev-shm-usage to the chrome flags fix the issue for you?

https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#tips

ZengTianShengZ · 2024-02-04T02:35:09Z

Does adding --disable-dev-shm-usage to the chrome flags fix the issue for you?

https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#tips

I retest and get the same results.

lighthouse-service-app-d84d67d8f-8r6zm:/app# sudo lighthouse  --verbose https://baidu.com  --enable-error-reporting --disable-dev-shm-usage --chrome-flags="--no-sandbox --headless --disable-gpu" --output=json
  LH:ChromeLauncher:verbose created /tmp/lighthouse.uD3FcQQ +0ms
  LH:ChromeLauncher:verbose Launching with command:
  LH:ChromeLauncher:verbose "/usr/bin/chromium-browser" --disable-features=Translate,OptimizationHints,MediaRouter,DialMediaRouteProvider,CalculateNativeWinOcclusion,InterestFeedContentSuggestions,CertificateTransparencyComponentUpdater,AutofillServerCommunication --disable-extensions --disable-component-extensions-with-background-pages --disable-background-networking --disable-component-update --disable-client-side-phishing-detection --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-default-browser-check --no-first-run --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-timer-throttling --disable-ipc-flooding-protection --password-store=basic --use-mock-keychain --force-fieldtrials=*BackgroundTracing/default/ --disable-hang-monitor --disable-prompt-on-repost --disable-domain-reliability --remote-debugging-port=40237 --disable-setuid-sandbox --user-data-dir=/tmp/lighthouse.uD3FcQQ --no-sandbox --headless --disable-gpu about:blank +5ms
  LH:ChromeLauncher:verbose Chrome running with pid 1902 on port 40237. +8ms
  LH:ChromeLauncher Waiting for browser. +0ms
  LH:ChromeLauncher Waiting for browser... +0ms
  LH:ChromeLauncher Waiting for browser..... +507ms
  LH:ChromeLauncher Waiting for browser.....✓ +1ms
  LH:status:verbose Initialize config +1ms
  LH:status:verbose Resolve artifact definitions +3ms
  LH:statusEnd:verbose Resolve artifact definitions +104ms
  LH:statusEnd:verbose Initialize config +826ms
  LH:status:verbose Gather phase +0ms

adamraine · 2024-02-05T06:08:13Z

You need to add it to --chrome-flags:

udo lighthouse  --verbose https://baidu.com/  --enable-error-reporting --chrome-flags="--disable-dev-shm-usage --no-sandbox --headless --disable-gpu" --output=json

ZengTianShengZ · 2024-02-05T07:12:03Z

I readjusted the test command, but it still stuck.

Miindaugas · 2024-03-11T23:13:07Z

I tried run in on alpine node:21.7.0-alpine3.19 to generate reports for my nextjs applicaiton.

--disable-dev-shm-usage did help. Thank you.

✅ npx lighthouse http://localhost:8080 --chrome-flags="--headless --disable-dev-shm-usage"

lhci lighthouserc.json

{
  "ci": {
    "collect": {
      "startServerCommand": "npm start",
      "settings": {
         "chromeFlags": "--headless --disable-dev-shm-usage",
       },
      "url": ["http://localhost:8080"]
    }
  }
}

FROM node:21.7.0-alpine3.19 AS test

ENV APP_ENV development
ENV NODE_ENV development
ENV NEXT_TELEMETRY_DISABLED 1

RUN apk add chromium

RUN mkdir /app
RUN mkdir /source

RUN addgroup --system --gid 1001 app-users
RUN adduser -D --system --uid 1001 --home /app app-user app-users
RUN chown -R app-user:app-users /app
RUN chown -R app-user:app-users /source

WORKDIR /app

COPY --from=build_test --chown=app-user:app-users /source /source
COPY --from=build_test --chown=app-user:app-users /source/public ./public
COPY --from=build_test --chown=app-user:app-users /source/.next/standalone ./
COPY --from=build_test --chown=app-user:app-users /source/.next/static ./.next/static

USER app-user

EXPOSE 8080
ENV PORT 8080
ENV HOSTNAME 0.0.0.0

dillonbarker-te · 2024-03-21T14:08:43Z

In our case,

Adding --headless will make it work, but we need it to be headless false.

So --headless is what fixes it, not the --disable-dev-shm-usage

My output is below

npx lighthouse "https://www.google.com" --verbose --output=json ----disable-storage-reset --output=html --output-path='test.html' --port=8041 ----screenEmulation.disabled ----preset desktop

 LH:ChromeLauncher Found existing Chrome already running using port 8041, using that. +0ms
 LH:status:verbose Initialize config +2ms
 LH:status:verbose Resolve artifact definitions +2ms
 LH:statusEnd:verbose Resolve artifact definitions +83ms
 LH:statusEnd:verbose Initialize config +481ms
 LH:status:verbose Gather phase +1ms

We see after 10 minutes we get

LH:status Connecting to browser +10m`

node: v20.11.1
lighthouse: 11.7.0
puppeteer: 22.6.0

We occasionally when escaping the command will see the same log as shown in this puppeteer log.

puppeteer/puppeteer#7807

ZengTianShengZ · 2024-04-28T05:50:53Z

Is there any progress on this issue? I still cannot run Lighthouse normally in my scenario.

ZengTianShengZ added the bug label Feb 1, 2024

github-actions bot assigned connorjclark Feb 1, 2024

ZengTianShengZ mentioned this issue Feb 2, 2024

Lighthouse User Flow doens't work in Docker #15796

Open

2 tasks

devtools-bot added the needs-priority label Feb 4, 2024

adamraine added the needs-investigation label Feb 6, 2024

adamraine assigned adamraine and unassigned connorjclark Mar 5, 2024

adamraine added P3 and removed needs-priority labels Mar 5, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Executing lighthouse lic gets stuck in alpine nodejs environment #15793

Executing lighthouse lic gets stuck in alpine nodejs environment #15793

ZengTianShengZ commented Feb 1, 2024

adamraine commented Feb 2, 2024

ZengTianShengZ commented Feb 4, 2024

adamraine commented Feb 5, 2024

ZengTianShengZ commented Feb 5, 2024

Miindaugas commented Mar 11, 2024 •

edited

dillonbarker-te commented Mar 21, 2024 •

edited

ZengTianShengZ commented Apr 28, 2024

Executing lighthouse lic gets stuck in alpine nodejs environment #15793

Executing lighthouse lic gets stuck in alpine nodejs environment #15793

Comments

ZengTianShengZ commented Feb 1, 2024

FAQ

URL

What happened?

What did you expect?

What have you tried?

How were you running Lighthouse?

Lighthouse Version

Chrome Version

Node Version

OS

Relevant log output

adamraine commented Feb 2, 2024

ZengTianShengZ commented Feb 4, 2024

adamraine commented Feb 5, 2024

ZengTianShengZ commented Feb 5, 2024

Miindaugas commented Mar 11, 2024 • edited

dillonbarker-te commented Mar 21, 2024 • edited

ZengTianShengZ commented Apr 28, 2024

Miindaugas commented Mar 11, 2024 •

edited

dillonbarker-te commented Mar 21, 2024 •

edited