Skip to content

docker.md

Latest commit

 

History

History
90 lines (64 loc) · 2.66 KB

docker.md

File metadata and controls

90 lines (64 loc) · 2.66 KB

Docker Configurations for Next.js

This directory contains Docker configurations for running Next.js applications in both development and production environments.

Directory Structure

docker/
├── Dockerfile.development - Development container with hot reloading
├── Dockerfile.production - Production-optimized multi-stage build
├── docker-compose.development.yml - Development environment with mounted volumes
└── docker-compose.production.yml - Production environment configuration

Development Environment

The development Docker setup provides:

  • Hot reloading for immediate feedback during development
  • Volume mounting of the source code
  • Isolated node_modules directory
  • Development-specific environment variables

Usage

# Start the development environment
cd docker
docker-compose -f docker-compose.development.yml up

# Stop the development environment
docker-compose -f docker-compose.development.yml down

Production Environment

The production Docker setup features:

  • Multi-stage build for optimized image size
  • Running as a non-root user for enhanced security
  • Health checks for container monitoring
  • Resource limits for better predictability
  • Only including necessary files

Usage

# Build and start the production environment
cd docker
docker-compose -f docker-compose.production.yml up -d

# Check container status
docker-compose -f docker-compose.production.yml ps

# View logs
docker-compose -f docker-compose.production.yml logs -f

# Stop the production environment
docker-compose -f docker-compose.production.yml down

Best Practices

Security

  • The production Dockerfile runs as a non-root user (nextjs)
  • Only necessary files are included in the final image
  • NODE_ENV is set to production, disabling development features
  • Health checks ensure the application is responding correctly

Performance

  • Multi-stage builds reduce the final image size
  • Only production dependencies are included
  • Next.js telemetry is disabled
  • Resource limits prevent container resource abuse

Development Workflow

  • Source code is mounted for immediate feedback
  • Node modules are isolated to prevent host/container conflicts
  • Environment variables can be easily configured for development

Common Pitfalls

  1. Node Modules Conflicts - Ensure node_modules isn't mounted from host to container
  2. Build Context - The build context matters for relative paths in Dockerfiles
  3. Environment Variables - Make sure to pass all required environment variables
  4. Permissions - Watch for permission issues when mounting volumes
  5. Caching - Be aware of Docker's caching mechanisms during builds