<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Volumes on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/volumes/</link><description>Recent content in Volumes on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 19 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/volumes/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (4): Networking and Volumes — How Containers Talk and Persist</title><link>https://www.chenk.top/en/docker-containers/04-networking-and-volumes/</link><pubDate>Mon, 19 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/04-networking-and-volumes/</guid><description>&lt;p>Containers are deliberately isolated. That&amp;rsquo;s the point. But useful applications need to accept connections from the outside world, talk to databases, and store data that survives container restarts. Docker provides two mechanisms for this: networks (for communication) and volumes (for persistent storage). Getting these right makes the difference between a demo and a deployment.&lt;/p>
&lt;hr>
&lt;h2 id="docker-networking" class="heading-anchor">Docker Networking&lt;a href="#docker-networking" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>When Docker starts, it creates a virtual network infrastructure on the host. Each container gets its own network namespace (with its own IP address, routing table, and network interfaces), and Docker manages the traffic flow between containers and the outside world.&lt;/p></description></item></channel></rss>