Docker containerization for Node.js in Node.js - Mini Project: Build & Apply

Docker containerization for Node.js

📖 Scenario: You are building a simple Node.js app that says hello. You want to package it inside a Docker container so it can run anywhere easily.

🎯 Goal: Create a Docker container for a Node.js app that listens on port 3000 and responds with 'Hello from Docker!'.

📋 What You'll Learn

Create a basic Node.js app with Express that listens on port 3000

Add a configuration variable for the port number

Write a Dockerfile to containerize the app

Run the app inside the Docker container exposing port 3000

💡 Why This Matters

🌍 Real World

Docker lets developers package apps with all dependencies so they run the same on any computer or server.

💼 Career

Knowing Docker containerization is essential for modern backend and full-stack developers to deploy and manage applications efficiently.

1

Create the Node.js app

Create a file called app.js with these exact lines: import express, create an app, and add a route / that sends the text 'Hello from Docker!'. Then make the app listen on port 3000.

Node.js

# Your code here to create app.js with express, route, and listen on port 3000

Hint

Use import express from 'express' and app.get for the route.

2

Add a port configuration variable

Add a constant called PORT and set it to 3000. Change the app.listen call to use this PORT variable.

Node.js

import express from 'express';
const app = express();

app.get('/', (req, res) => {
  res.send('Hello from Docker!');
});

// Define PORT variable and use it in app.listen
# Your code here

Hint

Define const PORT = 3000 and use app.listen(PORT).

3

Write the Dockerfile

Create a file called Dockerfile with these exact lines: start from node:18-alpine image, set working directory to /app, copy package*.json and app.js into the container, run npm install, expose port 3000, and run the app with node app.js.

Node.js

# Your Dockerfile content here

Hint

Use FROM node:18-alpine and CMD ["node", "app.js"].

4

Run the Docker container

Write the exact Docker command to build an image named node-hello from the current directory, then write the command to run a container from node-hello exposing port 3000 on the host.

Node.js

# Your Docker build and run commands here

Hint

Use docker build -t node-hello . and docker run -p 3000:3000 node-hello.

Practice

1. What is the main purpose of using Docker with a Node.js application?

easy

A. To make the app run only on Windows machines

B. To write Node.js code faster

C. To replace the need for npm packages

D. To package the app and its environment so it runs consistently anywhere

Solution

1. Step 1: Understand Docker's role

   Docker packages an app with everything it needs to run, including system libraries and settings.

2. Step 2: Apply this to Node.js apps

   This means your Node.js app will behave the same on any machine with Docker installed.

3. Final Answer:

   To package the app and its environment so it runs consistently anywhere -> Option D

4. Quick Check:

   Docker ensures consistent app environment = A [OK]

Hint: Docker bundles app + environment for consistent runs [OK]

Common Mistakes:

• Thinking Docker speeds up coding
• Believing Docker replaces npm
• Assuming Docker limits OS compatibility

2. Which of the following is the correct first line in a Dockerfile for a Node.js app using Node version 18?

easy

A. FROM node:18

B. RUN node 18

C. INSTALL node@18

D. USE node version 18

Solution

1. Step 1: Identify Dockerfile syntax for base image

   The Dockerfile starts with FROM followed by the image name and tag, e.g., node:18.

2. Step 2: Check options for correct syntax

   Only 'FROM node:18' correctly specifies the base image for Node.js version 18.

3. Final Answer:

   FROM node:18 -> Option A

4. Quick Check:

   Dockerfile base image starts with FROM = B [OK]

Hint: Dockerfile base image line always starts with FROM [OK]

Common Mistakes:

• Using RUN instead of FROM for base image
• Writing INSTALL which is not a Dockerfile command
• Using USE which is invalid in Dockerfile

3. Given this Dockerfile snippet:

FROM node:18
WORKDIR /app
COPY package.json ./
RUN npm install
COPY . .
CMD ["node", "index.js"]

What happens when you build and run this container?

medium

A. The container fails because CMD syntax is wrong

B. The container runs the Node.js app starting at index.js after installing dependencies

C. The container runs npm install every time it starts

D. The container only copies files but does not install dependencies

Solution

1. Step 1: Analyze Dockerfile commands

   WORKDIR sets /app, COPY adds package.json, RUN npm install installs dependencies, COPY . . adds all files, CMD runs node index.js.

2. Step 2: Understand build vs run behavior

   npm install runs during build, so dependencies are ready when container runs. CMD starts the app.

3. Final Answer:

   The container runs the Node.js app starting at index.js after installing dependencies -> Option B

4. Quick Check:

   RUN npm install during build, CMD runs app = D [OK]

Hint: RUN commands execute at build, CMD runs app at container start [OK]

Common Mistakes:

• Thinking npm install runs at container start
• Believing CMD syntax is invalid
• Assuming dependencies are not installed

4. You wrote this Dockerfile:

FROM node:18
WORKDIR /app
COPY . .
RUN npm install
CMD node index.js

But when you build and run, the app does not start correctly. What is the likely problem?

medium

A. COPY . . should be before FROM node:18

B. WORKDIR should be set after RUN npm install

C. CMD should be an array like ["node", "index.js"] instead of a string

D. npm install should be RUN npm start

Solution

1. Step 1: Check CMD syntax

   CMD can be a string or array, but string form runs via shell which can cause issues. Array form is recommended for direct exec.

2. Step 2: Identify best practice for Node.js Dockerfiles

   Using CMD ["node", "index.js"] avoids shell parsing problems and ensures correct app start.

3. Final Answer:

   CMD should be an array like ["node", "index.js"] instead of a string -> Option C

4. Quick Check:

   Use array form for CMD to start Node app correctly = A [OK]

Hint: Use array syntax for CMD to avoid shell issues [OK]

Common Mistakes:

• Placing COPY before FROM
• Confusing RUN npm install with RUN npm start
• Changing WORKDIR order unnecessarily

5. You want to optimize your Node.js Docker image to avoid reinstalling dependencies if only source code changes. Which Dockerfile change helps achieve this?

hard

A. Copy only package.json and package-lock.json first, run npm install, then copy the rest of the app files

B. Run npm install before copying any files

C. Copy all files first, then run npm install

D. Use RUN npm install every time the container starts

Solution

1. Step 1: Understand Docker layer caching

   Docker caches layers; if package.json doesn't change, npm install layer is reused.

2. Step 2: Optimize Dockerfile order

   Copy package.json and package-lock.json first, run npm install, then copy app files to avoid reinstalling dependencies on code changes.

3. Final Answer:

   Copy only package.json and package-lock.json first, run npm install, then copy the rest of the app files -> Option A

4. Quick Check:

   Separate dependency files copy before install = C [OK]

Hint: Copy package files first to cache npm install layer [OK]

Common Mistakes:

• Running npm install before copying files
• Copying all files before npm install
• Running npm install at container start