<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wsl2 on Danilo Falcão da Silva</title><link>https://falcao.org/tags/wsl2/</link><description>Recent content in Wsl2 on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 20 Jun 2026 20:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/wsl2/index.xml" rel="self" type="application/rss+xml"/><item><title>WSL Containers: What Actually Changes If You Already Live in WSL2</title><link>https://falcao.org/posts/wsl-containers-what-changes-for-wsl2-users/</link><pubDate>Sat, 20 Jun 2026 20:00:00 -0300</pubDate><guid>https://falcao.org/posts/wsl-containers-what-changes-for-wsl2-users/</guid><description>&lt;p>If you have already fixed WSL2 networking twice this quarter, you read the Build 2026 headlines differently than everyone else. While the tech press argued about whether Microsoft just shipped &amp;ldquo;WSL 3,&amp;rdquo; you were the person who actually had to make Docker Desktop, a corporate VPN, and &lt;code>kubectl&lt;/code> agree on DNS before standup. So when a wave of articles announced that a paravirtualized GPU/NPU future had arrived, my first question was not &amp;ldquo;is this exciting.&amp;rdquo; It was &amp;ldquo;does this change the thing that breaks on my machine.&amp;rdquo;&lt;/p></description></item></channel></rss>