You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extract all files in the zip file to the same directory.
Run Arch.exe to Extract rootfs and Register to WSL.
4.run command: systemctl start systemd-networkd-wait-online.service
Expected behavior
Job for systemd-networkd-wait-online.service failed because the control process exited with error code.
See "systemctl status systemd-networkd-wait-online.service" and "journalctl -xeu systemd-networkd-wait-online.service"for details.
Screenshots
If applicable, add screenshots to help explain your problem.
Enviroment:
Microsoft Windows [Version 10.0.22631.3447]
WSL2
ArchWSL version 24.4.28.0
ArchWSL Installer type zip
Launcher version 24042000
Additional context
When starting docker, I found that the startup time was very long, and I found that it was caused by service systemd-networkd-wait-online.service startup timeout. Then I tried to start service systemd-networkd-wait-online.service separately. The result was that the service could not be started.
The text was updated successfully, but these errors were encountered:
IMPORTANT
Please read README and Docs before creating the issue.
Please fill out the below information:
Describe the issue
systemd-networkd-wait-online.service is start timeout.
To Reproduce
Steps to reproduce the behavior:
4.run command: systemctl start systemd-networkd-wait-online.service
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Enviroment:
Additional context
When starting docker, I found that the startup time was very long, and I found that it was caused by service systemd-networkd-wait-online.service startup timeout. Then I tried to start service systemd-networkd-wait-online.service separately. The result was that the service could not be started.
The text was updated successfully, but these errors were encountered: