Docker Tag 0.9.0 Not Released

[philwc]

Describe the bug

In this commit (https://github.com/GoogleChrome/lighthouse-ci/commit/fe181b61b20205dba5962c40094b1c90983f1c5e) the tag for the docker image has been updated to 0.9.0, however, the image has not been pushed to docker hub (https://hub.docker.com/r/patrickhulce/lhci-server/tags)

To Reproduce Steps to reproduce the behavior:

1. Go to https://hub.docker.com/r/patrickhulce/lhci-server/tags'
2. Verify 0.9.0 is not in the list of tags

Expected behavior 0.9.0 is available to pull

[kutzi]

Any update on this issue? Would be nice if we could use the latest release with Docker @connorjclark ?

[connorjclark]

I've just published the latest version to dockerhub, could someone verify it's working on their end?

[kutzi]

Can confirm that server starts and is able to read old data volume. Will now check if publishing with the new client works

[kutzi]

lhci-client doesn't look so good:

[2022-03-24T15:45:14.823Z] Running Lighthouse 5 time(s) on ...
[2022-03-24T15:48:24.975Z] Run #1...failed!

[2022-03-24T15:48:24.975Z] Error: Lighthouse failed with exit code 1

[2022-03-24T15:48:24.975Z]     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/@lhci/cli/src/collect/node-runner.js:120:21)

[2022-03-24T15:48:24.975Z]     at ChildProcess.emit (events.js:400:28)

[2022-03-24T15:48:24.975Z]     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)

[2022-03-24T15:48:24.975Z] Thu, 24 Mar 2022 15:45:14 GMT LH:ChromeLauncher Waiting for browser.

[2022-03-24T15:48:24.975Z] Thu, 24 Mar 2022 15:45:14 GMT LH:ChromeLauncher Waiting for browser...

[2022-03-24T15:48:24.975Z] Thu, 24 Mar 2022 15:45:15 GMT LH:ChromeLauncher Waiting for browser.....

[2022-03-24T15:48:24.975Z] Thu, 24 Mar 2022 15:45:15 GMT LH:ChromeLauncher Waiting for browser.....✓

...

[2022-03-24T15:48:24.976Z] Thu, 24 Mar 2022 15:46:17 GMT LH:ChromeLauncher Killing Chrome instance 85

[2022-03-24T15:48:24.976Z] Runtime error encountered: Waiting for DevTools protocol response has exceeded the allotted time. (Method: Network.emulateNetworkConditions)

[2022-03-24T15:48:24.976Z] LHError: PROTOCOL_TIMEOUT

[2022-03-24T15:48:24.976Z]     at /usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/gather/driver.js:341:50

[2022-03-24T15:48:24.976Z]     at new Promise (<anonymous>)

[2022-03-24T15:48:24.976Z]     at Driver.sendCommandToSession (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/gather/driver.js:339:28)

[2022-03-24T15:48:24.976Z]     at Driver.sendCommand (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/gather/driver.js:362:17)

[2022-03-24T15:48:24.976Z]     at clearNetworkThrottling (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/lib/emulation.js:135:18)

[2022-03-24T15:48:24.976Z]     at Object.clearThrottling (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/lib/emulation.js:107:22)

[2022-03-24T15:48:24.976Z]     at Function.runPass (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/gather/gather-runner.js:591:21)

[2022-03-24T15:48:24.976Z]     at processTicksAndRejections (internal/process/task_queues.js:95:5)

[2022-03-24T15:48:24.976Z]     at async Function.run (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/gather/gather-runner.js:509:29)

[2022-03-24T15:48:24.976Z]     at async Function._gatherArtifactsFromBrowser (/usr/local/lib/node_modules/@lhci/cli/node_modules/lighthouse/lighthouse-core/runner.js:237:23)

[kutzi]

Didn't change anything except the image. With the old lhci-client image it was and still is (against the new server) working.

[kutzi]

Seems to be related to https://github.com/GoogleChrome/lighthouse/issues/6512#issuecomment-1029150960

I've added the custom chrome option --disable-dev-shm-usage as suggested and now it seems to run stable

[JuanCruzTrinidad]

One question, I did the same upgrade, but it didn't work for me. The server doesn't even start, I'm using the postgresql database. In your case, which database option do you use?

[kutzi]

In your case, which database option do you use?

I just started it with the standard options given in the readme: docker container run --publish 80:9001 --mount='type=volume,src=lhci-data,target=/data' --name lhci-server --detach patrickhulce/lhci-server Not sure which DB option that is.

[JuanCruzTrinidad]

By the explication, db options is a sqlite, or database local in the docker container. In caise search the persistence, i have a bug whit postgreSQL. https://github.com/GoogleChrome/lighthouse-ci/issues/775

[connorjclark]

Is the new 0.10.0 image any better?