/mnt/wsl is uninitialized affecting resolv.conf with no visibility into why

[Josh-Marshall-FactSet]

Windows Version

Microsoft Windows [Version 10.0.22631.2861]

WSL Version

2.0.9, 2.0.14, 2.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.137.3-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04 LTS

Other Software

No response

Repro Steps

I have uninstalled everything, followed the installation procedure here (https://learn.microsoft.com/en-us/windows/wsl/install#prerequisites) at wsl --install and I have my error. resolve.conf, it is a dangling link. This is because /mnt/wsl is not populated and appears to 'just' be uninitialized. There is nothing in the Event Viewer about an error or issue. No warnings from WSL. No obvious errors in journalctl or systemctl services. No errors from the WSL debug console except for the DNS lookup errors which are caused by the aforementioned missing resolve.conf. I'm really at a loss here.

Expected Behavior

/mnt/wsl/resolv.conf should exist with the header noting that it has been automatically generated by WSL and the typical DNS entries it populates.

Actual Behavior

Absence of any behavior.

Diagnostic Logs

Not yet applicable. I require direction on what information to gather.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• wsl.conf generateResolvConf = false always deleted /etc/resolv.conf (#9074), similarity score: 0.71

Closed similar issues:

• /etc/resolv.conf always automatically made, and ignores /etc/wsl.conf (#5527), similarity score: 0.73

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Josh-Marshall-FactSet]

One thing of note during my day of debugging is that there are many, many pages of resolve.conf changing or getting over-written, but this is the first I've ran into of it missing. If someone can point me to where the logging in for where WSL creates and updates files in /mnt/wsl, that is sure to make this bug easy.

[OneBlue]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

[ivarprudnikov]

Posted my steps to regenerate resolv.conf in #11928 (comment)