<?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 Hambz</title>
    <link>/tags/docker/</link>
    <description>Recent content in docker on Hambz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© Halladj Hamza</copyright>
    <lastBuildDate>Tue, 26 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/docker/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>Ever since I have heard about containers technology, I have had a foggy understanding of Docker images. The terms layered-architecture, and multi-layer build 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.
File-system mounts: Before we dive deeper into our topic, we must build a good understanding of what are file-system (FS) mounts and how they work.</description>
    </item>
    
    <item>
      <title>Docker&#39;s No Nonsense Tour</title>
      <link>/posts/post-10/</link>
      <pubDate>Wed, 27 Jul 2022 00:00:00 +0000</pubDate>
      
      <guid>/posts/post-10/</guid>
      <description>Before docker was a thing, developing, testing and shipping software was a huge miss and it is still a miss afterward, don&amp;rsquo;t get me wrong but at the end of this article, you might appreciate how docker made the process more bearable, those are some of the technologies used to develop software without using docker:
 Virtual Machines package management systems config management tools a pile of interconnected dependencies.  Meaning each team member of the different teams involved in the development process would have to get that huge pile of miss to work locally, you could imagine how painful that would be, that&amp;rsquo;s where docker comes into play, where it gives the ability to contain the entire software stack and published it(publicly or privately) as an image for the members to use, by use I mean just running a simple command such</description>
    </item>
    
  </channel>
</rss>
