<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Kailun's Blog</title><link>https://elated-hopper-5c0cb3.netlify.app/tags/docker/</link><description>Recent content in Docker on Kailun's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 23 May 2020 19:29:09 -0700</lastBuildDate><atom:link href="https://elated-hopper-5c0cb3.netlify.app/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Network and Linux Network Namespace</title><link>https://elated-hopper-5c0cb3.netlify.app/posts/docker-network/</link><pubDate>Sat, 23 May 2020 19:29:09 -0700</pubDate><guid>https://elated-hopper-5c0cb3.netlify.app/posts/docker-network/</guid><description>&lt;p&gt;In Docker we can create a new network using &lt;code&gt;docker network create&lt;/code&gt; with several options. In this post we will take a look at some Linux networking concepts that are used, the basic Docker networking concepts, and how we can use these to construct a custom container network.&lt;/p&gt;
&lt;h1 id="network-namespaces"&gt;Network Namespaces&lt;/h1&gt;
&lt;p&gt;Docker leverages Linux network namespaces for network isolation, like the way it uses other namespaces (e.g. process namespaces, user namespaces). A network namespace provides a shared set of network interfaces, routing table, and firewall rules. Each Docker container has its own network namespace.&lt;/p&gt;</description></item></channel></rss>