<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting on ProHomeLab – everything about homelab and self-hosting</title><link>https://prohomelab.com/en/tags/troubleshooting/</link><description>Recent content in Troubleshooting on ProHomeLab – everything about homelab and self-hosting</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>pavel@prohomelab.com (Stilicho2011)</managingEditor><webMaster>pavel@prohomelab.com (Stilicho2011)</webMaster><copyright>&amp;copy; 2025-2026 Stilicho2011. All Rights Reserved.</copyright><lastBuildDate>Fri, 21 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://prohomelab.com/en/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Hit Its Network Limit: How I Diagnosed and Fixed It with default-address-pools</title><link>https://prohomelab.com/en/posts/docker-default-address-pools/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><author>pavel@prohomelab.com (Stilicho2011)</author><guid>https://prohomelab.com/en/posts/docker-default-address-pools/</guid><description>Breaking down a real case: after moving to a dedicated Docker network per compose stack, I hit the &lt;code&gt;could not find an available, non-overlapping IPv4 address pool&lt;/code&gt; limit. Why this happens, how to diagnose it, and how to fix it for good via &lt;code&gt;default-address-pools&lt;/code&gt; in &lt;code&gt;daemon.json&lt;/code&gt;.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://prohomelab.com/posts/docker-default-address-pools/featured.png"/></item></channel></rss>