Skip to main content

Installation of Windows Subsystem for Linux

Introduction:


I'm sure many saw this and wondered what this is. Let me explain.
This is known as Windows Subsystem for Linux(WSL). Basically, WSL is like a Linux Environment running on Windows without a need to have VM or Dual Boot.
WSL allows you to integrate your Linux Applications, Tools, directly inside Windows.
Refer What is Windows Subsystem for Linux | Microsoft Learn for more details.

Pre-requisites:

  • Basic Understanding of Linux
  • Basic Understanding of Virtual Machine 
  • Basic Understanding of OS Installation / Dual Boot

Books & References:

Demonstration:

1. Direct Installation via  wsl --install:

You can open PowerShell running as Administrator.

Note that this method is only available to Windows 10 version 2004 and higher (Build 19041 and higher) or Windows 11.

2. I will follow the Manual way of installation:

i. Enable Windows Subsystem for Linux:

Run the following command in Powershell with Administrator rights.
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart


ii. Enable Virtual Machine Feature:

Run the following command in Powershell with Administrator rights.

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

You will need your machine to have virtualization capabilities. Restart the machine to complete WSL install correctly.


iii. Download the Linux Kernel Update Package and Install:

You can get the package from Linux Kernel Update Package from here and run the installer.



iv. Set WSL2 as the default version:
Run the following command in Powershell with Administrator rights.
wsl --set-default-version 2


v. Install a Linux Distribution from Microsoft App Source:
Go to Microsoft App Source and install Ubuntu Linux Distro.


vi. Open the Linux Distribution App and complete User Setup:

You will see a CLI version of Ubuntu started asking for Username and Password.



vii. Setup a GUI through LXDE Desktop Environment:
I tried setting up LXDE Desktop Environment. However, it did not work as expected.

Conclusion:

I hope this blog clarifies what is WSL and how to setup. More follow-up blogs will come up soon.
For any questions feel free to reach out to me at olisterr@outlook.com

Cheers!!

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe