<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Commentary of Takao</title><link>https://takao.blog/ko/tags/networking/</link><description>Recent content in Networking on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>ko</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sun, 12 Jul 2026 04:12:51 +0900</lastBuildDate><atom:link href="https://takao.blog/ko/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Networking: From Bridge to Overlay Networks</title><link>https://takao.blog/ko/web/docker-networking/</link><pubDate>Tue, 27 Aug 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/ko/web/docker-networking/</guid><description>&lt;img src="https://takao.blog/img/thumbnail/docker-networking-ko.png" alt="Featured image of post Docker Networking: From Bridge to Overlay Networks" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;Docker containers are designed to be portable and isolated, but they rarely run in isolation. Containers need to communicate with each other, with the host system, and with external services. Understanding Docker&amp;rsquo;s networking model is essential for building reliable, secure, and performant containerized applications.&lt;/p&gt;
&lt;p&gt;Docker provides several built-in 네트워크 drivers — bridge, host, overlay, macvlan, ipvlan, and none — each suited to different use cases. This 가이드 covers each driver in depth, along with DNS 해상도, port mapping, security isolation, and Docker Compose networking patterns.&lt;/p&gt;</description></item></channel></rss>