{"slug": "i-used-docker-before-i-understood-it", "title": "I Used Docker Before I Understood It", "summary": "A developer recounts their journey of using Docker multiple times before truly understanding it, from running Ollama with WebUI and n8n automations to experimenting with Hyperledger and an observability stack during an internship. They now aim to move beyond blindly running commands to understanding Docker's internals, including images, containers, volumes, and networks.", "body_md": "I've used Docker several times.\n\nThe funny part?\n\nI didn't really understand Docker.\n\nMy first encounter with it was back in March 2026, when I was exploring different automations and customizations. One of the things I wanted to try was running Ollama with WebUI locally. I wanted a local AI model with a nice interface, and Docker happened to be part of the setup.\n\nAt the time, I wasn't very well versed with AI/LLM terminology or what was actually happening underneath. I just wanted the thing to work. 😅\n\nThat wasn't the last time I used Docker.\n\nMy next encounter was when I was trying out an n8n automation.\n\nI was frustrated with how many hackathon alerts I was missing because of chaotic WhatsApp groups. So I wanted to build a workflow that could filter the messages I cared about and send useful information to a Telegram node.\n\nDocker was involved in getting n8n running.\n\nAt the time, though, Docker was basically just another command I had to run to make the thing work.\n\nEventually, running all of this started taking a toll on my poor laptop. I had storage and RAM issues, so I ended up removing Docker and later switched to running n8n using a `.bat` script.\n\nI still didn't really understand Docker.\n\nThen Docker showed up again while I was experimenting with Hyperledger and blockchain.\n\nThe idea was to use the blockchain infrastructure to store logs for a demonstration. Docker was involved in getting the required services running.\n\nOnce again, I was using Docker because the setup instructions told me to.\n\nI could make it work.\n\nI couldn't really explain why it worked.\n\nThis was probably the point where I started appreciating Docker.\n\nDuring my internship, I had to work with an observability stack involving tools like Grafana, Prometheus and the ELK stack, along with a few other services.\n\nInstead of manually installing and configuring every single component on my laptop, I could use Docker and Docker Compose to bring the environment up.\n\nThat was the first time I really noticed the value of it.\n\nI remember seeing another intern manually setting up some of these tools while I could bring up several services together through Docker.\n\nAnd I thought:\n\n\"Oh. This is actually pretty useful.\"\n\nThis is where I am currently in my learning journey.\n\nThe simplest way I can currently explain Docker to myself is that it lets you package an application together with the environment it needs and run that package consistently on systems that support Docker.\n\nThat sounds obvious now.\n\nIt didn't when I started.\n\nI used to think of Docker as some complicated way of installing software.\n\nNow I'm beginning to understand the difference between images, containers, volumes, networks and the Docker engine.\n\nI have also started thinking about Docker somewhat like the Java/JVM world I am familiar with.\n\nIt's not a perfect analogy, but the idea helps me:\n\nA Docker image is somewhat like a blueprint, while a container is an instance created from that image.\n\nAgain, this isn't literally how the two systems work. It's just an analogy that helps me reason about it while I'm learning.\n\nQuite a lot. 😂\n\nI have used Dockerfiles without really understanding everything happening inside them.\n\nI've run Docker Compose configurations without always understanding why every service, network or volume was there.\n\nI've pulled images from registries and run containers without thinking too deeply about what happens between the command and the running application.\n\nAnd I definitely don't understand Docker's internals yet.\n\nSo that's what I want to change.\n\nInstead of blindly running commands and hoping they work, I want to understand:\n\nBasically, I want to stop being the person who says:\n\n\"Run this command. It worked for me.\"\n\nand become the person who can actually explain why the command works.\n\nLooking back, I've probably used Docker more times than I realized.\n\nn8n.\n\nOllama and WebUI.\n\nHyperledger.\n\nMy internship observability stack.\n\nAnd now, finally, Docker itself.\n\nIt's kind of funny that I am learning the tool properly only after repeatedly using it.\n\nMaybe that's not such a bad way to learn after all.\n\n**PS:** Turns out I used n8n the first time for n8n, and Ollama + WebUI later.\n\nWell... I do have a terrible memory. 😂\n\nAt one point I even made a custom UI to replace WebUI.\n\nThis was before I realized that I was, in fact, terrible at frontend design.\n\nWe all start somewhere. 😭", "url": "https://wpnews.pro/news/i-used-docker-before-i-understood-it", "canonical_source": "https://dev.to/athrva1302/i-used-docker-before-i-understood-it-3fdj", "published_at": "2026-09-07 17:37:34+00:00", "updated_at": "2026-09-07 18:02:06.640056+00:00", "lang": "en", "topics": ["developer-tools"], "entities": ["Docker", "Ollama", "WebUI", "n8n", "Hyperledger", "Grafana", "Prometheus", "ELK stack"], "alternates": {"html": "https://wpnews.pro/news/i-used-docker-before-i-understood-it", "markdown": "https://wpnews.pro/news/i-used-docker-before-i-understood-it.md", "text": "https://wpnews.pro/news/i-used-docker-before-i-understood-it.txt", "jsonld": "https://wpnews.pro/news/i-used-docker-before-i-understood-it.jsonld"}}