<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog · Bosun</title>
    <link>https://bosun.dev/en/blog/</link>
    <description>Guides on ports, tunnels, VPN, and Docker networking on macOS. From the team behind Bosun.</description>
    <language>en-us</language>
    <atom:link href="https://bosun.dev/en/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Desktop eating CPU on your Mac? How to find (and kill) the culprit</title>
      <link>https://bosun.dev/en/blog/docker-desktop-high-cpu-mac/</link>
      <guid>https://bosun.dev/en/blog/docker-desktop-high-cpu-mac/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <description>Fan spinning and Mac sluggish because of Docker Desktop? Find out if it&apos;s Docker overall or one container, and what actually fixes the CPU spike.</description>
    </item>
    <item>
      <title>Docker: &quot;bind: address already in use&quot; on Mac (lsof won&apos;t tell you which container)</title>
      <link>https://bosun.dev/en/blog/docker-port-already-allocated-mac/</link>
      <guid>https://bosun.dev/en/blog/docker-port-already-allocated-mac/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <description>Docker port conflicts on Mac don&apos;t show up in lsof the way you&apos;d expect. Find the real container with docker ps, stop it the right way, and stop guessing.</description>
    </item>
    <item>
      <title>ngrok says tunnel already running (ERR_NGROK_108 / ERR_NGROK_334)? Here&apos;s the fix</title>
      <link>https://bosun.dev/en/blog/ngrok-tunnel-already-running-mac/</link>
      <guid>https://bosun.dev/en/blog/ngrok-tunnel-already-running-mac/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <description>Fix ngrok&apos;s ERR_NGROK_108 and ERR_NGROK_334 tunnel-already-running errors on Mac: find the orphaned process, kill it, and check what&apos;s actually tunneling.</description>
    </item>
    <item>
      <title>Port 3000 already in use on your Mac? Here&apos;s how to actually fix it</title>
      <link>https://bosun.dev/en/blog/port-3000-already-in-use-mac/</link>
      <guid>https://bosun.dev/en/blog/port-3000-already-in-use-mac/</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <description>Fix EADDRINUSE and &quot;port already in use&quot; errors on macOS: find the process with lsof, kill it the right way, and stop it from happening again.</description>
    </item>
  </channel>
</rss>
