Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fails to create tmp directory on WSL

See original GitHub issue

Provide the steps to reproduce

Run LH inside WSL2

What is the current behavior?

Runtime error encountered: EACCES: permission denied, mkdir '/mnt/undefined'
Error: EACCES: permission denied, mkdir '/mnt/undefined'
    at Object.mkdirSync (fs.js:750:3)
    at sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:71:13)
    at sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:77:24)
    at sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:77:24)
    at sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:77:24)
    at sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:77:24)
    at Function.sync (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/mkdirp/index.js:77:24)
    at makeWin32TmpDir (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/chrome-launcher/dist/utils.js:115:12)
    at Object.makeTmpDir (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/chrome-launcher/dist/utils.js:85:20)
    at Launcher.makeTmpDir (/home/villasv/.nvm/versions/node/v10.14.1/lib/node_modules/lighthouse/node_modules/chrome-launcher/dist/chrome-launcher.js:115:24)

What is the expected behavior?

No error.

Environment Information

Affected Channels: CLI
Lighthouse version: 5.6.0
Chrome version:
Node.js version: 10.14.1
Operating System: Ubuntu on Windows 10 WSL2

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:24 (8 by maintainers)

Top GitHub Comments

2reactions

michaelchichecommented, Feb 6, 2020

I am also having a problem with lighthouse inside WSL2.

It opens the chrome browser but then hangs with:

It looks like lighthouse succeeds to open chrome but cant seem to connect and manage it

1reaction

G-Rathcommented, May 15, 2020

the 6.0 release was just cut yesterday

🥳 you just made my day, as that will hopefully let us address the audit reports (I’ve not checked it out locally to run auditing against it, but seen PRs updating the dependencies that are being reported, so fingers crossed).

The beta is using 0.13.x - I remember seeing the PR; I’ll check it today if I have the time but otherwise use v6 on Monday 🥳🎉