Docker containerization for Node.js in Node.js - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the Dockerfile to specify the base image for a Node.js app.

Node.js

FROM [1]

Drag options to blanks, or click blank then click option'

Anode:18-alpine

Bpython:3.9

Cubuntu:latest

Dnginx:stable

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-Node.js base image like Python or Nginx.

Forgetting to specify a version tag.

The base image node:18-alpine is a lightweight Node.js image suitable for containerizing Node.js apps.

2fill in blank

medium

Complete the Dockerfile to copy the package.json file into the container.

Node.js

COPY [1] ./

Drag options to blanks, or click blank then click option'

Apackage.json

Bsrc/package.json

Capp.js

Dnode_modules

Attempts:

3 left

💡 Hint

Common Mistakes

Copying the wrong file like app.js or node_modules.

Using a wrong path like src/package.json when the file is in the root.

The package.json file is copied from the current directory to the container's working directory.

3fill in blank

hard

Fix the error in the Dockerfile command to install dependencies.

Node.js

RUN npm [1]

Drag options to blanks, or click blank then click option'

Astart

Btest

Cinstall

Dbuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using npm start which runs the app instead of installing.

Using npm build which is not a standard npm command.

The command npm install installs all dependencies listed in package.json.

4fill in blank

hard

Fill both blanks to set the working directory and copy all app files.

Node.js

WORKDIR [1]
COPY [2] ./

Drag options to blanks, or click blank then click option'

A/usr/src/app

Bsrc/

C.

D/app

Attempts:

3 left

💡 Hint

Common Mistakes

Using relative paths incorrectly for WORKDIR.

Copying from a wrong source directory like src/ when files are in root.

The working directory is set to /usr/src/app, and all files from the current directory . are copied into it.

5fill in blank

hard

Fill all three blanks to expose port 3000, set environment variable NODE_ENV to production, and define the command to start the app.

Node.js

EXPOSE [1]
ENV NODE_ENV=[2]
CMD ["npm", "[3]"]

Drag options to blanks, or click blank then click option'

Adevelopment

Bproduction

Cstart

D3000

Attempts:

3 left

💡 Hint

Common Mistakes

Exposing the wrong port number.

Setting NODE_ENV to development instead of production.

Using npm run or other commands instead of npm start.

Port 3000 is exposed, environment variable NODE_ENV is set to production, and the app is started with npm start.

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