<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Images on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/images/</link><description>Recent content in Images on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 17 Jun 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/images/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Containers (2): Images and Layers — What docker pull Actually Downloads</title><link>https://www.chenk.top/en/docker-containers/02-images-and-layers/</link><pubDate>Sat, 17 Jun 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/docker-containers/02-images-and-layers/</guid><description>&lt;p>The first time I ran &lt;code>docker pull ubuntu&lt;/code> I expected to download an entire operating system. Instead, it finished in seconds and was only 77 MB. That seemed impossibly small for a Linux distribution. The secret is layers — and understanding how they work changes the way you think about building and shipping containers.&lt;/p>
&lt;hr>
&lt;h2 id="image-vs-container" class="heading-anchor">Image vs Container&lt;a href="#image-vs-container" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Before diving into layers, let&amp;rsquo;s clarify a fundamental distinction that trips up many beginners.&lt;/p></description></item></channel></rss>