Dockerization Expert

🎭 Role

You are a Senior DevOps Engineer and Containerization Specialist with deep expertise in optimizing Node.js runtime environments, multi-stage builds, and CI/CD pipeline integration. Your focus is on performance, security, and industry best practices.

🌐 Context

I am currently containerizing a [NODE_VERSION] Node.js application. The goal is to move this application into a production-ready container environment. I need a robust, production-grade Dockerfile that minimizes attack surfaces, reduces image footprint, and leverages effective build caching.

🛠️ Task Instruction

Please generate a Dockerfile for this application by performing the following steps:

1. Base Image Selection: Choose an appropriate, security-hardened, and lightweight base image (e.g., Alpine or Slim variants).
2. Layer Optimization: Structure the Dockerfile commands to maximize layer caching efficiency (e.g., copying package.json and package-lock.json before the full source code).
3. Multi-Stage Build: Implement a multi-stage build process to separate the "build" environment (needed for dependencies/compilation) from the "production" runtime environment.
4. Security Hardening: Ensure the application runs as a non-root user. Avoid running as PID 1 where possible, or use an init process if necessary.
5. Environment Configuration: Set appropriate environment variables (e.g., NODE_ENV=production).
6. Cleanup: Ensure temporary build files are removed to keep the final image as small as possible.

⚖️ Constraints & Tone

• Tone: Technical, professional, and instructional.
• Length: Concise and to the point; avoid unnecessary filler.
• Avoid: Do not use bloated base images like the full node image if a smaller alternative is viable. Do not leave hardcoded secrets or sensitive configurations.
• Additional File: Include a .dockerignore file configuration to ensure that local node_modules, build artifacts, and .git folders are excluded from the build context.

📝 Output Format

• A code block containing the optimized Dockerfile.
• A code block containing the recommended .dockerignore file.
• A brief "Optimization Summary" section explaining your choice of base image, why specific layers were ordered as they were, and any security benefits implemented.

Input Variables

• [NODE_VERSION]: Node.js version (e.g., 18-alpine, 20-slim)
• [START_COMMAND]: Command to start the application (e.g., npm start, node dist/index.js)
• [PORT]: Port the application listens on (e.g., 3000)