<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>WSL on Mengboy Tech Notes</title>
    <link>https://www.mfun.ink/en/categories/wsl/</link>
    <description>Recent content in WSL on Mengboy Tech Notes</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 11 Feb 2026 22:50:00 +0800</lastBuildDate>
    <atom:link href="https://www.mfun.ink/en/categories/wsl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WSL2 &#43; Docker Network Troubleshooting: Fix DNS Timeouts and Image Pull Failures</title>
      <link>https://www.mfun.ink/en/2026/02/11/wsl2-docker-network-troubleshooting/</link>
      <pubDate>Wed, 11 Feb 2026 22:50:00 +0800</pubDate>
      <guid>https://www.mfun.ink/en/2026/02/11/wsl2-docker-network-troubleshooting/</guid>
      <description>&lt;p&gt;If your &lt;strong&gt;WSL2 + Docker&lt;/strong&gt; setup suddenly fails with &lt;code&gt;docker pull&lt;/code&gt; timeouts, &lt;code&gt;Temporary failure in name resolution&lt;/code&gt;, or containers that start but cannot access the internet, don&amp;rsquo;t nuke your environment yet. Most cases are recoverable in 15 minutes.&lt;/p&gt;
&lt;p&gt;This guide gives you a practical sequence: identify whether the fault is DNS, proxy/VPN, virtual NIC, or Docker daemon config—then apply the smallest fix first.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
