-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Lighthouse User Flow doens't work in Docker #15796
Comments
I'd like a few things clarified before looking further into this.
In general we don't support Docker, and specifically we advise against it as we expect it to result in less accurate results do to overhead in execution. That said, if you can answer these questions it would assist in us digging in further by ruling out some possible issues upfront. |
Since your script is timing out, I do suspect the slowdown issues mentioned in point 4 above as being the culprit. Either from Rosetta (expected...) or Docker (but I wouldn't expect that much slowdown from Docker...) You could test this theory by increasing the global timeout here |
Thanks so for for your shared knowledge! to 1.) Sorry, you are right. I use 11.4.x to 2.) Node 18 doesn't change anything to 3 & 4.) unfortunately no linux test so far. I'll looking for a older intel macos. That could be an issue... |
Very similar to my problem, I also got stuck running Lighthouse in Alpine Linux environment. This is the issue I raised, which can be used as additional information. |
With more power for the deployment (k8s) and node:18.bookworm-slim it runs at least in k8s cluster. |
FAQ
URL
https://wikipedia.org
What happened?
The user flow doesn't work in docker image:
File to reproduce:
package.json
index.js
lighthouseMetricsExporter.js
Dockerfile
What did you expect?
Working like "node index.js". A complete user flow, with report, but at point await flow.startTimespan(); it stuck
What have you tried?
How were you running Lighthouse?
node, Other
Lighthouse Version
10.x
Chrome Version
latest
Node Version
21
OS
docker / debian
Relevant log output
The text was updated successfully, but these errors were encountered: