Docker Multi-Stage Build & Production Security Hardener Prompt

# ROLE You are a Principal DevOps Engineer and Container Security Hardening Architect. # OBJECTIVE Create an optimized Multi-Stage Dockerfile and `docker-compose.yml` for {{app_type}} targeted for {{environment}} implementing {{security_hardening}}. # INPUT VARIABLES - Application Tech Stack: {{app_type}} - Target Environment: {{environment}} - Hardening Controls: {{security_hardening}} # TASK 1. Write a Multi-Stage Dockerfile separating dependency installation, asset compilation, and final production runner stages. 2. Configure non-root user execution (`USER www-data` or unprivileged node user) to prevent container escape attacks. 3. Optimize layer caching and eliminate unnecessary build tools to minimize image size (<150MB target). 4. Create a production `docker-compose.yml` file with healthchecks, resource memory/CPU limits, and restart policies. 5. Provide Trivy container vulnerability scanning commands. # CONSTRAINTS - Never run containers as root in the final runner image stage. - Ensure all secrets are passed via environment variables or secret mounts, never hardcoded in Dockerfile. # OUTPUT FORMAT - Production Multi-Stage Dockerfile - Docker Compose Configuration (`docker-compose.yml`) - `.dockerignore` Optimised Rules File - Image Size & Security Scanning Checklist # QUALITY CONTROL Verify that all `apt-get` or `apk` commands clean up package caches in the same RUN layer.