The issue with WSL2 on Unbuntu24.04 is that it cannot connect to the Windows network

[KTXKIKI]

Windows Version

Microsoft Windows [版本 10.0.26100.2605]

WSL Version

2.4.8

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Nov 5 00:21:55 UTC 2024

Distro Version

ubuntu 24.04

Other Software

docker desktop windows 4.37.1

Repro Steps

2025-01-04T21:45:03.340012+08:00 KTX-LEGION wsl-pro-service[182]: #33[36mINFO#033[0m Reconnecting to Windows host in 60 seconds
2025-01-04T21:45:03.340025+08:00 KTX-LEGION wsl-pro-service[182]: #33[37mDEBUG#033[0m Updated systemd status to "Not connected: waiting to retry"
2025-01-04T21:45:23.116061+08:00 KTX-LEGION systemd-resolved[131]: Clock change detected. Flushing caches.
2025-01-04T21:45:55.845380+08:00 KTX-LEGION systemd-resolved[131]: message repeated 3 times: [ Clock change detected. Flushing caches.]
2025-01-04T21:46:05.907860+08:00 KTX-LEGION wsl-pro-service[182]: #33[36mINFO#033[0m Daemon: connecting to Windows Agent
2025-01-04T21:46:05.907965+08:00 KTX-LEGION wsl-pro-service[182]: #33[37mDEBUG#033[0m Updated systemd status to "Connecting"
2025-01-04T21:46:05.908081+08:00 KTX-LEGION wsl-pro-service[182]: #33[33mWARNING#033[0m Daemon: could not connect to Windows Agent: could not get address: could not read agent port file "/mnt/c/Users/www17/.ubuntupro/.address": open /mnt/c/Users/www17/.ubuntupro/.address: no such file or directory

Expected Behavior

Why doesn't it work again after building a few containers? It gets stuck and doesn't move anymore

Actual Behavior

Why doesn't it work again after building a few containers? It gets stuck and doesn't move anymore

Is it due to Ubuntu 24.04?

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

• WSL2 no internet/net connection (#10421), similarity score: 0.71
• No network connection in any distribution under WSL2 (#11131), similarity score: 0.71

Closed similar issues:

• Network is unreachable in WSL 2 in Windows 10 build 19042 (#6295), similarity score: 0.71
• WSL2 ERROR (#12231), similarity score: 0.71
• Network "disappears" all of a sudden (WSL2/Win11) (#8861), similarity score: 0.71

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

[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!