<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bridge Network on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/bridge-network/</link><description>Recent content in Bridge Network on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/bridge-network/index.xml" rel="self" type="application/rss+xml"/><item><title>The Container Conversation - Docker Networking Basics</title><link>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-06-docker-networking/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-06-docker-networking/</guid><description>&lt;h2 id="the-container-conversation---docker-networking-basics"&gt;The Container Conversation - Docker Networking Basics&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring Docker master! In our previous chapters, you&amp;rsquo;ve learned how to wrangle individual containers, build your own images, and even manage persistent data. That&amp;rsquo;s fantastic! You&amp;rsquo;re already doing more than just running simple commands.&lt;/p&gt;
&lt;p&gt;But what happens when your application isn&amp;rsquo;t just one isolated container? What if you have a web server container, a database container, and an API container, all needing to talk to each other? How do they find each other? How do they communicate securely? And how do users outside your Docker host access your applications? This is where Docker networking comes into play, and it&amp;rsquo;s a fundamental skill for building real-world, multi-container applications.&lt;/p&gt;</description></item></channel></rss>