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
Remove /etc/wsl.conf file.
wsl --shutdown
Create .wslconfig file in C:\Users\<UserName> with the following content:
[boot]systemd=true
[interop]# Restrict launching Windows processes in WSLenabled=false
# Do not appent Windows PATH to WSL $PATHappendWindowsPath = false
NOTE: there is another issue that .wslconfig file should have LF line endings. Otherwise, with CRLF, it doesn't work in my setup.
Start the WSL and see output in Terminal:
wsl: Unknown key 'boot.systemd' in C:\Users\root\.wslconfig:2
wsl: Unknown key 'interop.enabled' in C:\Users\root\.wslconfig:6
wsl: Unknown key 'interop.appendWindowsPath' in C:\Users\root\.wslconfig:9
Also, see that, for example, docker inside WSL isn't accessible because systemd doesn't start due to broken .wslconfig. Windows or WSL reboot doesn't fix this problem.
Expected Behavior
WSL configuration successfully loaded from C:\Users\<UserName>\.wslconfig file.
Actual Behavior
Errors when loading WSL configuration from C:\Users\<UserName>\.wslconfig file.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
Windows Version
Microsoft Windows [Version 10.0.22621.2283]
WSL Version
2.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.123.1-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Remove /etc/wsl.conf file.
wsl --shutdown
Create .wslconfig file in
C:\Users\<UserName>
with the following content:NOTE: there is another issue that .wslconfig file should have LF line endings. Otherwise, with CRLF, it doesn't work in my setup.
Start the WSL and see output in Terminal:
Also, see that, for example, docker inside WSL isn't accessible because systemd doesn't start due to broken .wslconfig.
Windows or WSL reboot doesn't fix this problem.
Expected Behavior
WSL configuration successfully loaded from
C:\Users\<UserName>\.wslconfig
file.Actual Behavior
Errors when loading WSL configuration from
C:\Users\<UserName>\.wslconfig
file.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: