Master Docker from Zero to Deployment: A Hands‑On Guide for Modern Developers

1. Story Introduction

To make Docker easier to understand, the article starts with a story: you build a house, then a magician gives you a "image" that lets you copy the house and move it anywhere, just like Docker images let you package and redeploy applications instantly.

2. Virtual Machines vs. Containers

A virtual machine (VM) emulates full hardware, runs a complete OS, and isolates resources but is heavy and slow to start. Containers virtualize only the OS layer, share the host kernel, start instantly, use far fewer resources, and are ideal for rapid scaling.

VMs provide strong isolation but consume gigabytes of space and take minutes to boot.

Containers run in lightweight sandboxes, need only megabytes, and start in seconds.

3. What Is Docker?

Docker is an open‑source container engine that packages applications and their dependencies into portable images. Its three core concepts are Image, Container, and Repository.

Why Docker Is Lightweight

Docker leverages Linux kernel features (namespaces, cgroups) to isolate processes without a full OS, enabling the “Build once, Run anywhere” model.

4. Core Docker Concepts

Build

, Ship and Run – the three steps of container workflow. Build once, Run anywhere – create an image once and deploy it on any host.

Docker itself is not a container; it is the tool that creates and manages containers.

Docker uses Linux kernel isolation (namespaces, cgroups); on macOS/Windows it runs a lightweight Linux VM.

An image contains code, runtime, libraries, environment variables and config files; a container is a running instance of an image.

5. Installing Docker

On macOS you can install Docker via Homebrew Cask: brew cask install docker Check the version: docker -v Configure a registry mirror (example JSON configuration):

{
  "registry-mirrors": [
    "http://hub-mirror.c.163.com/",
    "https://registry.docker-cn.com"
  ],
  "insecure-registries": [],
  "experimental": false,
  "debug": true
}

6. Quick Start: Deploy a Vue App with Nginx

Create a Vue project: vue create docker-demo Build the project: yarn build Create a Dockerfile: cd docker-demo && touch Dockerfile Pull the official Nginx image: docker pull nginx Write default.conf for Nginx (simplified):

server {
    listen 80;
    server_name localhost;
    location / {
        root /usr/share/nginx/html;
        index index.html index.htm;
    }
}

Populate the Dockerfile:

FROM nginx
COPY dist/ /usr/share/nginx/html/
COPY default.conf /etc/nginx/conf.d/default.conf

Build the image: docker build -t jartto-docker-demo . Run the container, mapping host port 3000 to container port 80:

docker run -d -p 3000:80 --name docker-vue jartto-docker-demo

Verify the container is running with docker ps -a and access the app at http://localhost:3000.

7. Common Dockerfile Instructions

FROM : specify the base image (must be the first command).

MAINTAINER : author information.

RUN : execute commands during image build.

ADD : copy files/directories and automatically extract archives.

COPY : copy files without extraction.

CMD : default command when the container starts (overridable).

ENTRYPOINT : command that cannot be overridden by docker run arguments.

LABEL : add metadata key‑value pairs.

ENV : set environment variables.

EXPOSE : declare the port the container listens on.

VOLUME : define mount points for persistent data.

WORKDIR : set the working directory for subsequent commands.

USER : specify the user to run commands as.

ARG : define build‑time variables.

8. Best Practices

Clearly define the required image.

Minimize the number of layers; combine related steps.

Tag images with explicit version numbers.

Document the build process so it can be reproduced.

9. Conclusion

Containerization is essential in the cloud era, and Docker is just the beginning; mastering it paves the way to advanced orchestration tools like Kubernetes, Service Mesh, and Istio.