DEV Community

Cover image for 🚀 Day 9 of My Cloud Journey: Mastering Docker Volumes, Compose & Registry
Avinash wagh
Avinash wagh

Posted on

🚀 Day 9 of My Cloud Journey: Mastering Docker Volumes, Compose & Registry

#devops #aws #docker #cloudcomputing

When I started learning Docker, running containers felt exciting. But very quickly, I ran into a practical question:

👉 What happens to my data when a container stops or gets deleted?

That’s when I realized — containers are ephemeral by design, and real-world applications need persistent storage, multi-service orchestration, and efficient image management.

So today, I explored three critical Docker concepts:
Volumes, Docker Compose, and Docker Registry 🐳

🧩 Why This Matters

In modern cloud applications, we rarely run a single container. Instead, we deal with:

  • Databases that must retain data
  • Backend and frontend services running together
  • Applications deployed across environments

Handling all this manually is not scalable. Docker provides powerful solutions to simplify these challenges.

📦 1. Understanding Docker Volumes (Persistent Storage)

Containers are temporary, but data should not be.

Docker Volumes solve this problem by storing data outside the container lifecycle.

🔹 What I Learned

  • Volumes persist data even if containers are removed
  • They are managed by Docker and are more reliable than container storage
  • Ideal for databases like MySQL, PostgreSQL, etc.

🔹 Hands-on 

docker volume create my-volume

docker run -d \
  --name mysql-db \
  -v my-volume:/var/lib/mysql \
  mysql
Enter fullscreen mode Exit fullscreen mode

✔️ Even after removing the container, the data remains safe

⚙️ 2. Docker Compose (Managing Multi-Container Apps)

Running multiple containers manually can quickly become messy.

Docker Compose allows us to define and manage multi-container applications using a single YAML file.

🔹 What I Learned

  • Define services, networks, and volumes in one place
  • Start all services with a single command
  • Makes development and testing much easier

🔹 Sample docker-compose.yml 

version: '3'
services:
  db:
    image: mysql
    container_name: mysql-db
    environment:
      MYSQL_ROOT_PASSWORD: root
    volumes:
      - db-data:/var/lib/mysql

  app:
    image: flask-app
    container_name: flask-app
    ports:
      - "5000:5000"
    depends_on:
      - db

volumes:
  db-data:
Enter fullscreen mode Exit fullscreen mode

▶️ Run everything 

docker compose up -d
Enter fullscreen mode Exit fullscreen mode

✔️ Multiple services running together with one command

🌐 3. Docker Registry (Image Management)

Once applications are built, they need to be shared and deployed.

Docker Registry helps store and distribute images across environments.

🔹 What I Learned

  • Images can be pushed to repositories like Docker Hub
  • Enables easy deployment across teams and servers
  • Versioning helps manage application updates

🔹 Basic Workflow 

docker tag my-app username/my-app
docker push username/my-app
docker pull username/my-app
Enter fullscreen mode Exit fullscreen mode

✔️ Simplifies deployment and collaboration

💡 Key Takeaways

  • Volumes ensure data persistence
  • Docker Compose simplifies multi-container orchestration
  • Registry enables image sharing and deployment
  • These concepts are essential for real-world DevOps and cloud environments

🔄 My Learning Reflection

Today’s learning shifted my mindset from:
👉 “Running containers”
to
👉 “Designing real-world, scalable applications using Docker”

I’m starting to see how these concepts connect to tools like Kubernetes and cloud platforms like AWS.

📘 Learning in Public

I’m documenting my journey as I transition from .NET Developer to Cloud Engineer.

💬 Let’s Connect

If you're learning Docker, DevOps, or Cloud — I’d love to connect, learn, and grow together.

Feedback and suggestions are always welcome 🙌

Top comments (0)