Volumes & Networks in Compose
Explicit network segmentation, named volumes, and multi-service data sharing patterns
Skills taught: docker.compose-networks, docker.compose-volumes, docker.network-segmentation
Explicit networks in Compose
By default, all services in a Compose file share one network — every service can reach every other. For production-style security, you create explicit networks and attach only the services that need to communicate. A frontend and database should never share a network.
services:
# nginx reverse proxy — on both networks so it can route traffic
nginx:
image: nginx:alpine
ports:
- "80:80"
networks:
- frontend
- backend
volumes:
- ./nginx.conf:/etc/nginx/conf.d/default.conf
# API server — only on backend network
api:
build: .
networks:
- backend
environment:
DATABASE_URL: postgres://postgres:secret@db:5432/myapp
# Database — only on backend network (never reachable from frontend)
db:
image: postgres:16-alpine
networks:
- backend
environment:
POSTGRES_PASSWORD: secret
volumes:
- db-data:/var/lib/postgresql/data
# Define networks explicitly
networks:
frontend:
driver: bridge
backend:
driver: bridge
volumes:
db-data:
Volume patterns in Compose
services:
app:
image: myapp
volumes:
# Bind mount — great for dev hot-reload
- ./src:/app/src
# Named volume — persistent data
- app-data:/app/data
# Read-only bind mount — config file
- ./config.json:/app/config.json:ro
# Shared volume between two services
- shared-uploads:/app/uploads
worker:
image: myworker
volumes:
# Same named volume — both services access the same uploads
- shared-uploads:/worker/uploads
volumes:
app-data:
# driver options for custom storage backends
driver: local
shared-uploads:
# External volume: must exist before compose up
# external: true
# name: my-existing-volume
Compose override files — dev vs prod
# docker-compose.yml — base (shared between dev and prod)
# docker-compose.override.yml — auto-loaded in development
# docker-compose.prod.yml — explicit production overrides
# docker-compose.yml (base)
services:
api:
image: myapp-api
environment:
PORT: 3000
---
# docker-compose.override.yml (dev additions — auto-merged)
services:
api:
build: .
volumes:
- ./src:/app/src # hot reload
environment:
NODE_ENV: development
ports:
- "3000:3000"
---
# docker-compose.prod.yml (production)
services:
api:
image: ghcr.io/myorg/api:1.4.2
environment:
NODE_ENV: production
deploy:
replicas: 3
resources:
limits:
memory: 512m
# Development (auto-merges docker-compose.override.yml)
docker compose up -d
# Production (explicitly specify files)
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d
Frequently Asked Questions
What happens to named volumes when I run docker compose down?
Named volumes are preserved by default — 'docker compose down' stops and removes containers but keeps volumes. Your database data survives. To also delete volumes, run 'docker compose down -v' — but this permanently deletes all data in named volumes. Never run -v without knowing what data you're destroying.