<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containerization on Hambz</title><link>/tags/containerization/</link><description>Recent content in Containerization on Hambz</description><generator>Hugo</generator><language>en-us</language><copyright>© Halladj Hamza</copyright><lastBuildDate>Tue, 26 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/containerization/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Images Under the Hood</title><link>/posts/post-15/</link><pubDate>Tue, 26 Nov 2024 00:00:00 +0000</pubDate><guid>/posts/post-15/</guid><description>&lt;p>Ever since I have heard about containers technology, I have had a foggy understanding of Docker images. The terms &lt;em>layered-architecture&lt;/em>, and &lt;em>multi-layer build&lt;/em> have never made much sense to me, like I could comfortably write a dev-docker image or a deployment docker image, however I was never satified, sense my mental model of how it all works under-the-hook was not fully constructed.&lt;/p>
&lt;h2 id="file-system-mounts">File-system mounts:&lt;a class="heading-anchor" href="#file-system-mounts" aria-label="Link to this section">#&lt;/a>&lt;/h2>&lt;p>Before we dive deeper into our topic, we must build a good understanding of what are &lt;em>file-system (FS) mounts&lt;/em> and how they work. If you are already comfortable with these concepts please feel free to move to the next section.&lt;/p></description></item></channel></rss>