Docker Mastery Part 5: Advanced Networking, Volumes, and Best Practices

Introduction

In the final part of our series, we tackle the topics that separate the beginners from the pros: Data Persistence, Networking, and Image Optimization.

1. Docker Volumes (Data Persistence)

By default, data inside a container is ephemeral. If the container is removed, the data is lost. Volumes are the preferred mechanism for persisting data.

Types of Mounts:

1. Named Volumes: Managed by Docker. Best for database data.
   Copy

   docker volume create my-data
   docker run -v my-data:/app/data my-image
   

2. Bind Mounts: Maps a specific folder on your host machine to the container. Best for live code reloading during development.
   Copy

   docker run -v $(pwd)/src:/app/src my-image
   

2. Advanced Networking

Docker offers several network drivers:

• Bridge (Default): The default private network created for containers.
• Host: Removes network isolation between the container and the Docker host. The container shares the host's networking namespace.
  Copy

  docker run --network host my-image
  

• None: Completely disables networking.

3. Dockerfile Best Practices

1. Multi-Stage Builds

Drastically reduce image size by separating the build environment from the runtime environment.

# Stage 1: Build
FROM node:18 AS builder
WORKDIR /app
COPY . .
RUN npm install && npm run build

# Stage 2: Run
FROM nginx:alpine
COPY --from=builder /app/build /usr/share/nginx/html

2. Layer Caching

Order matters. Copy package.json and install dependencies before copying source code. This ensures Docker uses the cached layer for dependencies unless package.json changes.

3. Use .dockerignore

Prevent unnecessary files (node_modules, .git, logs) from being sent to the build context, speeding up builds and reducing image size.

Conclusion

Congratulations! You've completed the Docker Mastery series. You now possess the knowledge to build optimized images, orchestrate complex environments, and manage production-ready containers.