<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Antara Chakrabarti on Medium]]></title>
        <description><![CDATA[Stories by Antara Chakrabarti on Medium]]></description>
        <link>https://medium.com/@mailantara6?source=rss-d64d554177b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3Jhl1KUOQMWWxWJX</url>
            <title>Stories by Antara Chakrabarti on Medium</title>
            <link>https://medium.com/@mailantara6?source=rss-d64d554177b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:07:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mailantara6/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Chapter 2 — Dear Junior Devs, From “It Works on My Machine” to Running Your First Container]]></title>
            <link>https://medium.com/@mailantara6/chapter-2-dear-junior-devs-from-it-works-on-my-machine-to-running-your-first-container-a01f601d7c2d?source=rss-d64d554177b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a01f601d7c2d</guid>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[docker-image]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Antara Chakrabarti]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 13:11:48 GMT</pubDate>
            <atom:updated>2026-11-04T15:35:08.833Z</atom:updated>
            <content:encoded><![CDATA[<h4>In the world of technology, when programmers write an application, it is like a delicate receipe. It needs specific ingredients — libraries, code, settings and tools for the application to work properly. If you just hand the loose ingredients to someone else’s computer, it might not have right environment and fail. This is something we understood in our previous <a href="https://medium.com/@mailantara6/chapter-1-dear-junior-devs-this-is-the-chaos-we-endured-before-docker-existed-8f681cae19f5">chapter</a>.</h4><p>So, what do clever engineers do? They use a tool called <strong>Docker!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q-ZiqgGmvR--GM_4iQoSIg.png" /><figcaption>Legacy Chaos vs. Modern Container Harmony</figcaption></figure><p>Docker is a platform that helps us build and manage containers. To understand Docker, we need to understand two key terminologies — <br>1. Docker Image <br>2. Docker Container.</p><p>Let’s start with the image.</p><blockquote>Think of a <strong>Docker Image</strong> as the master blueprint for a house.</blockquote><blockquote>The blueprint It contains all the instructions, dimensions, and materials needed to construct the house.</blockquote><p>Similarly, a Docker image is a<strong> </strong>package containing everything needed to prepare your application’s runtime environment: your application code, runtime, libraries, dependencies, and configuration required inside the container. <br>Docker image is a <strong>read-only template</strong> that Docker uses to create containers.</p><p>But a blueprint is still just a blueprint.</p><blockquote>You cannot live inside a blueprint.</blockquote><p>To actually use it, you need to construct a house from it.</p><p>That’s where a <strong>Docker Container</strong> comes in.</p><p><strong>A Docker container is a</strong> <strong>running instance of an Docker image</strong>.</p><blockquote>If the Docker image is the blueprint, the Docker container is the actual house constructed from that blueprint. You can live inside it, change the color of the interior walls (write data), or turn the lights on and off (start/stop processes).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v2PpGz55-K5XtRaWEg7VCQ.png" /><figcaption>Docker Image vs. Docker Container</figcaption></figure><p>Because each container gets created from the same packaged image, therefore, the applications gets a much more <strong>consistent runtime environment</strong> whether you’re running it on your laptop, another developer’s machine, a test server, or a cloud server.</p><p>Using image, we can easily replicate our local environment in a standardised way across developers, teams, and environments.</p><p>Let’s look at some of their most important properties — <br><strong>1. Containers are Portable: </strong><br>Container as a unit can be shared across teams. In technical terms of Docker, we do not share the running container itself. Instead, we share the <em>Docker Image</em>.</p><p><strong>2. Containers Are Lightweight:</strong> <br>Containers generally have much less overhead than Virtual Machines and therefore, are much lighter than Virtual Machines. In the later part, we will know why it is so.</p><p><strong>3. Different Containers Can Have Different Dependency Versions:</strong><br>Suppose we’re developing <strong>two Node.js applications</strong>.<br>Application A requires: <strong><em>Node.js 16<br></em></strong>Application B requires: <strong><em>Node.js 20</em></strong></p><p>Now we have a problem. What if our laptop has <strong>Node.js 16</strong> installed?</p><p>Application A is good to go. But Application B wants Node.js 20.</p><p>Of course, there are other tools for managing multiple Node.js versions, but containers give us another powerful way to isolate these environments.</p><p>We can create:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McuafqzN1Lkuu5PPGbKFNQ.png" /></figure><p>Both containers can run on the <strong>same host machine</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD-mcyF2TVuIKOJHAgStlQ.png" /><figcaption><em>Different containers can run different runtime and dependency versions.</em></figcaption></figure><p>And here’s the powerful part:</p><blockquote>You can create <strong>multiple containers from the same Docker Image</strong>, just like you can construct multiple houses from the same blueprint.</blockquote><p>There is another important difference between an image and a running container —</p><p>A Docker Image is <strong>static</strong>. It exists on disk as a collection of read-only layers.An image <strong>consumes disk storage</strong>.</p><p>A running container is different.</p><p>Once the container starts running, its processes <strong>can consume runtime resources</strong> such as:</p><ul><li>CPU</li><li>Memory (RAM)</li><li>Network resources</li><li>Filesystem I/O</li></ul><p><em>To sum up we can say, docker container is a running instance whereas docker image is a static screenshot of what the local development environment should look like.</em></p><p>This was the fundamental difference between Docker image and a container.</p><p>In the next chapter, we’ll stop talking about containers…</p><p><strong>and actually run one. 🐳</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a01f601d7c2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 1 — Dear Junior Devs, This Is the Chaos We Endured Before Docker Existed]]></title>
            <link>https://medium.com/@mailantara6/chapter-1-dear-junior-devs-this-is-the-chaos-we-endured-before-docker-existed-8f681cae19f5?source=rss-d64d554177b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f681cae19f5</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Antara Chakrabarti]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 11:07:17 GMT</pubDate>
            <atom:updated>2026-11-03T13:12:41.821Z</atom:updated>
            <content:encoded><![CDATA[<p>Let us consider a hypothetical scenario. We have a Linux-based machine on which we are developing a Node.js application. The application happens to be built using Node.js version 16, with MongoDB version 4 serving as its database. All of this is configured within our local development environment.</p><p>Now, when we are working on personal projects, college assignments, or relatively modest applications, we seldom encounter the kind of complications that Docker is designed to eliminate. After all, when we are the sole architects, developers, and troubleshooters of our application, maintaining the development environment is hardly an insurmountable undertaking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DnmQYgfEpRmNkXx5NDRaFg.png" /><figcaption>Taming the local development setup — Node.js 16 and MongoDB 4, before the container era.</figcaption></figure><p>However, the situation assumes an entirely different complexion when we enter the ecosystem of a large organisation, where numerous developers, distributed across different teams and machines, collaborate on a single application.</p><p><strong>Imagine this.</strong></p><blockquote>It is your first day at a new organisation. You have just joined as a software developer, brimming with enthusiasm, eager to explore the codebase, understand the architecture, and perhaps even ship your first feature.</blockquote><blockquote>You open the project repository, clone the codebase, installed Node.js 26, assuming that using the latest available version is always the best choice, along with the latest version of MongoDB</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCFNpWdF18rM5xD12iiJCw.png" /><figcaption><em>“It works on their machine…”</em> — The immediate frustration of local version mismatch on your first day.</figcaption></figure><blockquote>After all, why would anyone deliberately install an older version of a technology when a newer one is available? So, you confidently run the application.</blockquote><blockquote>And then, reality strikes. <em>🤯</em></blockquote><blockquote><strong>The application refuses to start.</strong></blockquote><blockquote>You soon discover that the project requires specific versions of Node.js and MongoDB. It was originally developed and tested against Node.js 16 and a particular release of MongoDB 4.x. The newer versions you have installed might introduce breaking changes, altered behaviour, or compatibility issues with the application’s existing dependencies.</blockquote><blockquote>What you expected to be a productive first morning has turned into an exhausting exercise in installing dependencies, configuring environment variables, resolving version conflicts, and deciphering cryptic error messages.</blockquote><blockquote>And the irony?</blockquote><blockquote><strong>You haven’t even written a single line of code yet!</strong></blockquote><blockquote>Sounds familiar? Welcome to one of the most enduring headaches in software development: environment inconsistency.</blockquote><p>And these are merely a few manifestations of a much larger problem.</p><p>Some of the common challenges encountered in collaborative software development include:</p><ol><li><strong>Tedious and error-prone installation:</strong> <br>Every developer is required to manually install/configure each and every application’s dependencies, databases, runtimes, and other supporting software. The greater the number of developers, the greater the likelihood of inconsistencies and human error.</li><li><strong>Version incompatibility:</strong> <br>An application might have been developed and tested against a very specific version of Node.js, MongoDB, or some other dependency. <br>If a team member inadvertently installs a different version, the application might exhibit unexpected behaviour, encounter runtime errors, or fail altogether due to compatibility issues.</li><li><strong>Operating system discrepancies:</strong> <br>A command, system utility, or native dependency that functions perfectly on a Linux machine might behave differently or fail to work on macOS or Windows. <br>Differences in filesystem conventions, shell environments, system libraries, and operating system dependencies can introduce an additional layer of complexity.</li><li><strong>Inconsistent production environments</strong>: <br>Developing an application successfully on our local machine is only half the journey.<br>Eventually, the same application has to be deployed to a production server, where it will be used by real users. And this is where things can become troublesome.<br>The very problems we encounter while setting up our local development environment can follow us into production as well.<br>After all, our objective is not merely to make the application work on our own computer; it is to ensure that it works just as reliably on the production server.<br>Ideally, the production environment should be consistent with the environment in which the application was developed and tested. An application should not behave differently simply because it has moved from one machine to another.</li></ol><p>This brings us to quintessential lament of software developers everywhere — <strong>“But It Works on My Machine!”</strong></p><h3>Moving on to the Solution</h3><p>Tired of dependency hell? It’s time to see how we solve this.</p><p>Head over to <a href="https://medium.com/@mailantara6/chapter-2-dear-junior-devs-from-it-works-on-my-machine-to-running-your-first-container-a01f601d7c2d?postPublishedType=initial"><strong>Chapter 2 — Dear Junior Devs, From “It Works on My Machine” to Running Your First Container</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f681cae19f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>