Skip to content

Latest commit

 

History

History
198 lines (150 loc) · 10.1 KB

07a-troubleshooting-wsl-update.md

File metadata and controls

198 lines (150 loc) · 10.1 KB

Troubleshooting WSL Updates

This document outlines solutions to common issues encountered while updating the Windows Subsystem for Linux (WSL), helping ensure a smooth update process.

Table of Contents

  1. Issue 1: Update Error Code Wsl/Service/CreateInstance/0x80040326
  2. Issue 2: Network Resolution (DNS) Issues
  3. Issue 3: Configuring communication between Windows and WSL

Issue 1: Update Error Code Wsl/Service/CreateInstance/0x80040326

If you receive this error code when trying to update, it typically indicates an issue with the WSL service.

Solution 1: Update WSL

To resolve it, run the following command in your PowerShell or Command Prompt with administrator privileges:

wsl --update

After updating, restart your computer and try running the command again to ensure the update is applied.

Solution 2: Reinstall WSL

Ensure your Windows system is up-to-date, as outdated system components can interfere with WSL updates. If the error still persists, consider reinstalling WSL:

  1. Uninstall WSL: Open PowerShell as an administrator and run:

    dism.exe /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
dism.exe /online /disable-feature /featurename:VirtualMachinePlatform /norestart

  2. Reinstall WSL: Re-enable the WSL and Virtual Machine Platform features:

    dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

  3. Restart Your Machine: Restart your computer to finalize the reinstallation.

Issue 2: Network Resolution (DNS) Issues

If you experience network-related issues, such as the following error:

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary failure resolving 'archive.ubuntu.com'

This is often happens due to DNS resolution errors in WSL. To check it, see the content of /etc/resolv.conf by running:

cat /etc/resolv.conf

If the nameserver entry indicates, for example, the IP-address of your DSL, like nameserver 172.23.112.1, you need to change.

Solution 1: Update DNS Settings in /etc/resolv.conf

  1. Edit /etc/resolv.conf:

    • Open the WSL Terminal.
    • Edit the DNS resolver configuration file: 
      sudo vim /etc/resolv.conf
    • Change the nameserver entry (type i to enter insert mode) to use Google's DNS by replacing it with 8.8.8.8.
    • Save and close the file (type Esc, type :wq, press Enter).

  2. Set DNS Using a Command: Alternatively, set the DNS directly with this command:

    sudo sh -c "echo nameserver 8.8.8.8 > /etc/resolv.conf"

    This command updates the nameserver in /etc/resolv.conf to Google's DNS. Once updated, retry the WSL update command.

Following these steps should resolve most DNS-related update issues in WSL.

Solution 2: Enable Automatic DNS Resolution

If WSL is not automatically updating DNS settings, configure it to do so:

  1. Check /etc/wsl.conf: Ensure the following configuration is present:

    sudo vim /etc/wsl.conf

    Add or update the [network] section to enable automatic DNS:

    [network]
generateResolvConf = true

  2. Restart WSL: Restart the WSL service:

    wsl --shutdown
wsl

Solution 3: Reset WSL Network Configuration

If the issue persists, reset the WSL network configuration:

  1. Open PowerShell as an administrator and run:

    netsh winsock reset

  2. Restart your machine to apply changes.

  3. Restart WSL and check if the issue is resolved.

Tip

These solutions should address most update and DNS-related issues encountered with WSL. If problems persist, consult the official WSL documentation or seek assistance from the community forums.

Issue 3: Configuring communication between Windows and WSL

When using Windows Subsystem for Linux (WSL), it is common to encounter issues with communication between Windows and WSL services. This section provides solutions to help configure communication between Windows and WSL.

By default, the areg.init configuration file uses the localhost IP address to run the mcrouter and logcollector services on the Windows platform. Applications running within WSL cannot connect to these services due to this configuration. To resolve this, you need to modify the areg.init file settings to enable proper communication.

Important

  • Windows-to-WSL Connections: If a Windows-based client needs to connect to a router running in WSL, the default localhost settings should work without additional changes. See Solution 2

  • Networking Mode in WSL:

    • The default WSL networking mode is NAT (Network Address Translation). With this mode, connections from WSL to Windows require changes to the areg.init configuration file.
    • Switching WSL to Mirror Networking Mode may allow the localhost setting to work seamlessly between Windows and WSL. However, this has not been fully tested.

For more details, refer to the official documentation on Mirrored Mode Networking. Networking modes can be adjusted either through the .wslconfig file or via the WSL Settings application.

Solution 1: Editing all IP address settings (Recommended)

When WSL applications cannot connect to services running on Windows due to the use of default localhost address, you can reconfigure the areg.init settings to enable communication. In the following example, let's consider the case where mcrouter is running on Windows and logcollector is running within WSL. Other services and/or applications that communicate with mcrouter or logcollector can be run on either Windows or WSL.

Steps:

  1. Identify IP Adresses

    • Run ipconfig on Windows to find the IP address for the Windows host.
    • Run ifconfig in the WSL terminal to find the IP address for WSL.

  2. Update WSL Configuration Edit the areg.init configuration file for applications running on WSL to specify the IP addresses of the mcrouter and logcollector services. Update the lines:

    router::*::address::tcpip = <windows-ip-address>
logger::*::address::tcpip = <wsl-ip-address>

    Replace <windows-ip-address> and <wsl-ip-address> with the IP addresses found in Step 1.

  3. Update Windows Configuration Edit the areg.init configuration file for applications running on Windows to specify the IP address of the mcrouter and logcollector services. Update the lines:

    router::*::address::tcpip = <windows-ip-address>
logger::*::address::tcpip = <wsl-ip-address>

  4. Restart Services After updating the configuration files, restart the relevant services (mcrouter, logcollector, etc.) to apply the changes.

Solution 2: Updating only necessary IP addresses

Applications running on Windows have access to the localhost IP Address within WSL, but applications within WSL do not have access to the localhost IP address of Windows. Therefore, it is only strictly necessary to update the configuration files to reflect the IP address of services running on Windows. For example, let's again consider the case where mcrouter is running on Windows and logcollector is running on WSL.

Steps:

  1. Identify IP Adresses

    • Run ipconfig on Windows to find the IP address for the Windows host.

  2. Update WSL Configuration Edit the areg.init configuration file for applications running on WSL to specify the IP addresses of the mcrouter and logcollector services. Update the lines:

    router::*::address::tcpip = <windows-ip-address>

    Replace <windows-ip-address> with the IP address found in Step 1. Leave the line logger::*::address::tcpip = localhost unchanged.

  3. Update Windows Configuration Edit the areg.init configuration file for applications running on Windows to specify the IP address of the mcrouter and logcollector services. Update the lines:

    router::*::address::tcpip = <windows-ip-address>

    Again, leave the line logger::*::address::tcpip = localhost unchanged.

  4. Restart Services After updating the configuration files, restart the relevant services (mcrouter, logcollector, etc.) to apply the changes.

Important

You cannot mix Solution 1 and Solution 2. The IP address of a service and/or application running on WSL must either be specified as <wsl-ip-address> or left unchanged in both configuration files. Leaving localhost in one configuration file but specifying <wsl-ip-address> in the other will prevent proper communication. See this description.

For further details on configuring network communication between Windows and WSL, refer to the official documentation: Accessing Network Applications with WSL.