containerization-patterns

What problem does it solve? Writing Dockerfiles and Docker Compose configurations from scratch often leads to bloated images, security risks like root processes, leaked secrets, and fragile service orchestration between development and production environments. ## Core Features & Use Cases - Dockerfile Best Practices: Multi-stage builds, non-root users, layer caching optimization, .dockerignore usage, and pinned base image versions. - Docker Compose Patterns: Service isolation, bind mounts for hot-reloading, healthcheck-based dependencies, private networks, and environment variable management via .env files. - Environment Separation: Distinct configurations for development (volumes, exposed ports, debug tools) versus production (resource limits, restart policies, structured logging). - Use Case: When containerizing a web application with a database, use this Skill to generate a multi-stage Dockerfile with a non-root user and a Compose file where the app waits for the database healthcheck before starting. ## Quick Start Ask the AI to write a production-ready Dockerfile and Docker Compose setup for your application following containerization best practices.