<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tech on 万屋猫Labs</title><link>https://yn-labs.com/en/categories/tech/</link><description>Recent content in Tech on 万屋猫Labs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 05 Apr 2026 00:00:00 +0900</lastBuildDate><atom:link href="https://yn-labs.com/en/categories/tech/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Desktop Was Too Heavy, So I Migrated to LazyDocker on WSL2</title><link>https://yn-labs.com/en/posts/lazydocker-wsl2-migration/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0900</pubDate><guid>https://yn-labs.com/en/posts/lazydocker-wsl2-migration/</guid><description>&lt;p&gt;Memory pressure in a development environment is a serious problem.&lt;br&gt;
Even with 32GB of RAM in your machine, running a browser, an IDE, and — more recently — a local LLM (Ollama and the like) at the same time will exhaust your resources in no time.&lt;/p&gt;
&lt;p&gt;Open Task Manager, and the processes sitting at the top are consistently &lt;strong&gt;Docker Desktop&lt;/strong&gt;-related processes and a bloated &lt;strong&gt;Vmmem&lt;/strong&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What is Vmmem?&lt;/strong&gt;&lt;br&gt;
It is the Windows-side process that manages the memory and CPU resources used by virtual machines such as WSL2.&lt;br&gt;
When you use memory on the WSL2 side, the memory usage of this Vmmem on the Windows side increases accordingly.&lt;/p&gt;</description></item></channel></rss>