<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>WSLv2 on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/wslv2/</link>
        <description>Recent content in WSLv2 on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 01 Mar 2021 10:00:00 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/wslv2/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[WSL2/Win10] Limit Resource Consumption of WSLv2</title>
            <link>https://www.nico-maas.de/posts/2021-03-01-wsl2-win10-limit-resource-consumption-of-wslv2/</link>
            <pubDate>Mon, 01 Mar 2021 10:00:00 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2021-03-01-wsl2-win10-limit-resource-consumption-of-wslv2/</guid>
            <description>&lt;p&gt;Windows Subsystem for Linux 2 has a big problem called &amp;ldquo;Vmmem&amp;rdquo; - it is the process WSL uses to allocate RAM for usage within its user context. That itself is all fine, however, there are many known &lt;a class=&#34;link&#34; href=&#34;https://github.com/microsoft/WSL/issues/4166&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;issues&lt;/a&gt; that show that even after closing your e.g. Debian session, this memory is not returned to the system. This is also valid for usage of Docker for Windows within the WSLv2 context (meaning using Docker in the &amp;ldquo;new-style&amp;rdquo; install, not with the old HyperV machine).&lt;/p&gt;</description>
        </item><item>
            <title>[WSL2/Win10] Install WSLv2</title>
            <link>https://www.nico-maas.de/posts/2021-02-25-wsl2-win10-install-wslv2/</link>
            <pubDate>Thu, 25 Feb 2021 10:00:00 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2021-02-25-wsl2-win10-install-wslv2/</guid>
            <description>&lt;p&gt;1.) Open an administrative Powershell and activate the WSL feature&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;2.) Activate the Virtual Machine Platform, afterwards reboot your computer&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;3.) Download and install the WSLv2 Linux Kernel package from &lt;a class=&#34;link&#34; href=&#34;https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi&lt;/a&gt; - another Reboot is needed afterwards&lt;/p&gt;&#xA;&lt;p&gt;4.) Set WSLv2 as default WSL - open an administrative Powershell and enter&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;wsl --set-default-version 2&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;5.) Install one or multiple operating systems in WSLv2 - you can find them &lt;a class=&#34;link&#34; href=&#34;https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-6---install-your-linux-distribution-of-choice&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;here&lt;/a&gt;. You can also install these &amp;ldquo;offline&amp;rdquo;, meaning without the need to use Windows Store. For the offline install, download the needed package from this &lt;a class=&#34;link&#34; href=&#34;https://docs.microsoft.com/en-us/windows/wsl/install-manual#downloading-distributions&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;link&lt;/a&gt;, then install it by doubleclicking on the Icon - or via Powershell with&lt;/p&gt;</description>
        </item></channel>
</rss>
