Optimize Dockerfiles and container orchestration

Optimize Dockerfile for development speed and production readiness

Multi-stage builds separate build dependencies from runtime—shaves off 60-80% of image size vs single-stage.

• · existing Dockerfile or project structure

• · multi-stage Dockerfile
• · layer caching strategy
• · build time comparison
• · security scan results

• · Docker
• · optional: Trivy or similar scanner

Docker installed; project uses containerization

Layer cache missed if RUN order wrong; secrets baked into image if not using BuildKit secrets; bloated image if dependencies not pruned

• · build context size audited to avoid unnecessary copies
• · health checks included in final image
• · security hardening (non-root, no secrets)