Docker containerization for Node.js in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Docker containerization in simple terms?

Docker containerization means putting your app and everything it needs into a small, portable box called a container. This box can run anywhere without changing anything.

beginner

Why use Docker for a Node.js app?

Docker helps run your Node.js app the same way on any computer or server. It avoids problems like missing files or different software versions.

beginner

What is a Dockerfile in Node.js projects?

A Dockerfile is a simple text file with instructions to build a Docker container. It tells Docker how to set up your Node.js app inside the container.

intermediate

How do you start a Node.js app inside a Docker container?

You write a command in the Dockerfile like CMD ["node", "app.js"]. This tells Docker to run your app when the container starts.

beginner

What is the role of npm install in a Dockerfile for Node.js?

It installs all the app's needed packages inside the container so your Node.js app has everything to run properly.

What does a Docker container include for a Node.js app?

A Only Node.js runtime

B Only app code

C App code, Node.js runtime, and dependencies

D Only system files

A Docker container bundles your app code, the Node.js runtime, and all dependencies so it runs anywhere.

Which file tells Docker how to build a Node.js container?

A package.json

B index.js

C README.md

D Dockerfile

The Dockerfile contains instructions to build the container for your Node.js app.

What command is used inside a Dockerfile to install Node.js packages?

A npm install

B npm run

C node install

D npm start

npm install installs all dependencies listed in package.json inside the container.

How do you run your Node.js app when the Docker container starts?

A Using CMD or ENTRYPOINT in Dockerfile

B By running npm install

C By opening a terminal inside container

D By editing package.json

The Dockerfile uses CMD or ENTRYPOINT to specify the command to run your app when the container starts.

Why is Docker useful for sharing Node.js apps?

A It makes apps run slower

B It ensures apps run the same everywhere

C It removes the need for Node.js

D It only works on Windows

Docker packages apps so they run the same on any computer or server, avoiding setup problems.

Explain how you would create a Docker container for a simple Node.js app.

Think about the steps to prepare the app and tell Docker how to run it.

Describe the benefits of using Docker containerization for Node.js development and deployment.

Focus on how Docker helps with app reliability and portability.

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