<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ananya-Gupta08</title>
    <description>The latest articles on DEV Community by Ananya-Gupta08 (@ananyagupta08).</description>
    <link>https://dev.to/ananyagupta08</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3743944%2F48141086-c977-4eaa-8696-f5d45f36ab44.jpeg</url>
      <title>DEV Community: Ananya-Gupta08</title>
      <link>https://dev.to/ananyagupta08</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ananyagupta08"/>
    <language>en</language>
    <item>
      <title>I Thought Docker Was About Making My App Work Everywhere. I Was Wrong.</title>
      <dc:creator>Ananya-Gupta08</dc:creator>
      <pubDate>Wed, 18 Nov 2026 18:57:47 +0000</pubDate>
      <link>https://dev.to/ananyagupta08/i-thought-docker-was-about-making-my-app-work-everywhere-i-was-wrong-43cd</link>
      <guid>https://dev.to/ananyagupta08/i-thought-docker-was-about-making-my-app-work-everywhere-i-was-wrong-43cd</guid>
      <description>&lt;p&gt;I Thought Docker Was About Making My App Work Everywhere. I Was Wrong.&lt;/p&gt;

&lt;p&gt;Every time I tried learning Docker, I'd come across the same phrase:&lt;/p&gt;

&lt;p&gt;"But it works on my machine!"&lt;/p&gt;

&lt;p&gt;And every time, I'd think, okay, but isn't that what hosting is for?&lt;/p&gt;

&lt;p&gt;I mean, we build an application locally, deploy it on a server or a hosting platform, and now people can access it from anywhere. So where exactly does Docker come in?&lt;/p&gt;

&lt;p&gt;For the longest time, I thought Docker was just another way of doing that.&lt;/p&gt;

&lt;p&gt;And honestly, the phrase &lt;em&gt;"works on my machine"&lt;/em&gt; wasn't helping either. I took it quite literally. I thought the whole point was to make something that worked on my laptop work on everyone else's laptop too.&lt;/p&gt;

&lt;p&gt;Which, in my head, was already a solved problem.&lt;/p&gt;

&lt;p&gt;So Docker just felt like an extra step I couldn't quite justify.&lt;/p&gt;

&lt;p&gt;Turns out, I was asking the wrong question.&lt;/p&gt;

&lt;p&gt;The problem Docker was trying to solve wasn't really &lt;em&gt;"How do I make my application available to everyone?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;It was more like:&lt;/p&gt;

&lt;p&gt;"How do I make sure this application runs the same way when I move it somewhere else?"6&lt;/p&gt;

&lt;p&gt;And those are two very different things.&lt;/p&gt;

&lt;p&gt;Let's say I've built a backend on my laptop. Everything works perfectly. I've got the right Node.js version, the required packages, environment variables, and whatever else my application needs.&lt;/p&gt;

&lt;p&gt;Now someone else tries running the same code.&lt;/p&gt;

&lt;p&gt;Their Node version is different. Maybe they're missing a dependency. Maybe something is configured differently.&lt;/p&gt;

&lt;p&gt;Same code. Different environment. Suddenly, things aren't working anymore.&lt;/p&gt;

&lt;p&gt;That's the "works on my machine" problem.&lt;/p&gt;

&lt;p&gt;Not that other people can't access my application, but that the application itself might not run properly in another environment.&lt;/p&gt;

&lt;p&gt;And that's where Docker started making sense.&lt;/p&gt;

&lt;h2&gt;
  
  
  So what does Docker actually do?
&lt;/h2&gt;

&lt;p&gt;The way I understand it now, Docker lets me package my application along with the dependencies and runtime setup it needs into an image.&lt;/p&gt;

&lt;p&gt;That image can then be used to run a container on another machine with a compatible container runtime.&lt;/p&gt;

&lt;p&gt;Instead of telling someone:&lt;/p&gt;

&lt;p&gt;"Install this version of Node, then these dependencies, configure this, make sure that is running..."&lt;/p&gt;

&lt;p&gt;I can give them a much more consistent starting point.&lt;/p&gt;

&lt;p&gt;Of course, it doesn't magically fix everything. Environment variables, databases, networking, storage, and differences between systems still matter.&lt;/p&gt;

&lt;p&gt;But it removes a lot of the "wait, what version are you using?" kind of problems.&lt;/p&gt;

&lt;p&gt;And that's a pretty big deal.&lt;/p&gt;

&lt;p&gt;The part that finally connected the dots&lt;/p&gt;

&lt;p&gt;I was working on MyVigi, a full-stack project, and had started splitting parts of its backend into separate services.&lt;/p&gt;

&lt;p&gt;There was a core backend, a notification service, an SOS service, and eventually an API gateway.&lt;/p&gt;

&lt;p&gt;Now I wasn't dealing with just one application process anymore.&lt;/p&gt;

&lt;p&gt;I had multiple services, different ports, and communication between them to think about.&lt;/p&gt;

&lt;p&gt;This is where Docker Compose became useful.&lt;/p&gt;

&lt;p&gt;Instead of starting and managing every service individually, I could define how they should run together and bring them up with a command.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose up -d
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And seeing those services running as containers made the concept feel a lot less abstract.&lt;/p&gt;

&lt;p&gt;I could finally see why I'd want a consistent way to set up and run an application, especially as it became more complicated.&lt;/p&gt;

&lt;p&gt;But wait, what about hosting?&lt;/p&gt;

&lt;p&gt;This was the part I'd been confusing from the beginning.&lt;/p&gt;

&lt;p&gt;Hosting answers where my application runs and how people can reach it.&lt;/p&gt;

&lt;p&gt;Docker helps with how my application and its dependencies are packaged and run.&lt;/p&gt;

&lt;p&gt;They're not competing solutions.&lt;/p&gt;

&lt;p&gt;I can run a Docker container on my own laptop. I can also run one on a cloud server. But simply putting an application inside a container doesn't mean it's suddenly available on the internet.&lt;/p&gt;

&lt;p&gt;I'd still need a server or hosting environment, appropriate networking, and possibly a domain.&lt;/p&gt;

&lt;p&gt;Docker doesn't replace all of that.&lt;/p&gt;

&lt;p&gt;It just solves a different part of the problem.&lt;/p&gt;

&lt;p&gt;So, did I misunderstand Docker completely?&lt;/p&gt;

&lt;p&gt;Pretty much. At least initially.&lt;/p&gt;

&lt;p&gt;I think what confused me was that Docker kept being introduced with a problem statement I didn't fully understand.&lt;/p&gt;

&lt;p&gt;I knew what deployment was. I knew applications ran on servers. And I kept trying to fit Docker into that same explanation.&lt;/p&gt;

&lt;p&gt;It wasn't until I separated making an application accessible from making an application run consistently that things started clicking.&lt;/p&gt;

&lt;p&gt;And using it in an actual project helped much more than memorising definitions ever did.&lt;/p&gt;

&lt;p&gt;I still have plenty to learn about Docker&lt;/p&gt;

&lt;p&gt;But at least now, when someone says &lt;em&gt;"It works on my machine,"&lt;/em&gt; I know what problem they're actually talking about.&lt;/p&gt;

&lt;p&gt;And no, the solution isn't necessarily to put the entire internet on my laptop.&lt;/p&gt;

</description>
      <category>docker</category>
      <category>webdev</category>
      <category>development</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
