Docker deployment in NextJS - Mini Project: Build & Apply

Docker Deployment for Next.js App

📖 Scenario: You have built a simple Next.js app and want to deploy it using Docker. Docker helps package your app with everything it needs to run anywhere.Imagine you want to share your app with friends or deploy it on a server easily. Docker makes this simple by creating a container that runs your app exactly the same way on any computer.

🎯 Goal: Build a Docker setup for a Next.js app that installs dependencies, builds the app, and runs it inside a container.You will create a Dockerfile step-by-step to prepare your app for deployment.

📋 What You'll Learn

Create a Dockerfile starting from the official Node.js image

Set the working directory inside the container

Copy package.json and package-lock.json to install dependencies

Copy the rest of the app files

Build the Next.js app inside the container

Expose the correct port

Set the command to start the Next.js app

💡 Why This Matters

🌍 Real World

Docker helps developers package their Next.js apps so they run the same on any computer or server, making deployment easier and more reliable.

💼 Career

Knowing how to Dockerize web apps is a valuable skill for developers working in teams or deploying apps to production environments.

1

Start Dockerfile with base image and working directory

Create a Dockerfile that starts with the base image node:18-alpine and sets the working directory inside the container to /app using WORKDIR.

NextJS

FROM node:18-alpine
# Set working directory
# Your code here

Hint

Use FROM to specify the base image and WORKDIR to set the folder inside the container.

2

Copy package files and install dependencies

Add lines to copy package.json and package-lock.json from your project folder to the container's /app folder. Then run npm install to install dependencies.

NextJS

FROM node:18-alpine
WORKDIR /app

# Copy package files and install dependencies
# Your code here

Hint

Use COPY to copy files and RUN npm install to install packages.

3

Copy app files and build the Next.js app

Copy all remaining app files to the container using COPY . .. Then add a line to build the Next.js app inside the container by running npm run build.

NextJS

FROM node:18-alpine
WORKDIR /app

COPY package.json package-lock.json ./
RUN npm install

# Copy app files and build the app
# Your code here

Hint

Use COPY . . to copy all files and RUN npm run build to build the app.

4

Expose port and set start command

Add a line to expose port 3000 using EXPOSE 3000. Then set the container start command to npm start using CMD ["npm", "start"].

NextJS

FROM node:18-alpine
WORKDIR /app

COPY package.json package-lock.json ./
RUN npm install

COPY . .
RUN npm run build

# Expose port and set start command
# Your code here

Hint

Use EXPOSE to open the port and CMD to set the start command.

Practice

1. What is the main purpose of using Docker for deploying a Next.js application?

easy

A. To write the Next.js code faster

B. To package the app with all dependencies for consistent running anywhere

C. To replace the need for React in the app

D. To automatically generate CSS styles

Solution

1. Step 1: Understand Docker's role

   Docker packages an app with its environment so it runs the same on any machine.

2. Step 2: Relate to Next.js deployment

   This packaging ensures the Next.js app and its dependencies work consistently everywhere.

3. Final Answer:

   To package the app with all dependencies for consistent running anywhere -> Option B

4. Quick Check:

   Docker ensures consistent app environment = A [OK]

Hint: Docker packages app and dependencies for consistent deployment [OK]

Common Mistakes:

• Thinking Docker speeds up coding
• Confusing Docker with React features
• Assuming Docker styles the app automatically

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

easy

A. FROM node:18-alpine

B. RUN node install 18

C. COPY node:18 /app

D. START node version 18

Solution

1. Step 1: Identify Dockerfile base image syntax

   The Dockerfile starts with FROM followed by the base image name and tag.

2. Step 2: Match Node.js 18 base image

   Node official images use 'node:18-alpine' for a lightweight Node 18 environment.

3. Final Answer:

   FROM node:18-alpine -> Option A

4. Quick Check:

   Dockerfile base image starts with FROM = B [OK]

Hint: Dockerfile starts with FROM and image name [OK]

Common Mistakes:

• Using RUN instead of FROM for base image
• Trying to COPY node version as a command
• Using START which is not a Dockerfile command

3. Given this Dockerfile snippet for Next.js deployment:

FROM node:18-alpine
WORKDIR /app
COPY package.json .
RUN npm install
COPY . .
RUN npm run build
CMD ["npm", "start"]

What happens when you run this Docker image?

medium

A. The app builds and starts serving on default port

B. The app installs dependencies but never builds

C. The app builds but fails to start

D. The Dockerfile causes a syntax error

Solution

1. Step 1: Analyze Dockerfile commands

   It sets working directory, copies package.json, installs dependencies, copies all files, builds app, then starts it.

2. Step 2: Understand CMD effect

   CMD runs 'npm start' which serves the built Next.js app on default port 3000.

3. Final Answer:

   The app builds and starts serving on default port -> Option A

4. Quick Check:

   Build then start with npm = C [OK]

Hint: RUN builds, CMD starts app in Dockerfile [OK]

Common Mistakes:

• Assuming build step is missing
• Thinking CMD does not start the app
• Believing Dockerfile syntax is wrong here

4. You wrote this Dockerfile for your Next.js app but get an error when running the container:

FROM node:18-alpine
WORKDIR /app
COPY . .
RUN npm install
RUN npm run build
CMD npm start

What is the likely cause of the error?

medium

A. npm run build should be replaced with npm build

B. COPY command should come after RUN npm install

C. WORKDIR must be set after RUN commands

D. CMD syntax is incorrect; it should be an array

Solution

1. Step 1: Check CMD syntax

   CMD should be an array like ["npm", "start"] to run correctly in Docker.

2. Step 2: Verify other commands

   COPY before npm install is fine; WORKDIR before RUN is correct; npm run build is valid.

3. Final Answer:

   CMD syntax is incorrect; it should be an array -> Option D

4. Quick Check:

   CMD needs array syntax = A [OK]

Hint: Use array syntax for CMD in Dockerfile [OK]

Common Mistakes:

• Writing CMD as a string instead of array
• Moving COPY after npm install unnecessarily
• Changing npm run build to npm build incorrectly

5. You want to deploy a Next.js app with Docker and ensure it listens on port 8080 instead of the default 3000. Which change should you make in your Dockerfile and app start command?

hard

A. Modify Dockerfile to FROM node:8080 and keep app default

B. Change CMD to ["npm", "start", "--port", "8080"] without app changes

C. Set ENV PORT=8080 and run CMD ["npm", "start"] with app configured to use process.env.PORT

D. Expose port 8080 but keep app listening on 3000

Solution

1. Step 1: Set environment variable for port

   Use ENV PORT=8080 in Dockerfile so app can read the port from environment.

2. Step 2: Ensure app uses process.env.PORT

   Next.js app must listen on process.env.PORT to respect Docker port setting.

3. Final Answer:

   Set ENV PORT=8080 and run CMD ["npm", "start"] with app configured to use process.env.PORT -> Option C

4. Quick Check:

   Use ENV and app reads process.env.PORT = D [OK]

Hint: Set ENV PORT and app reads process.env.PORT [OK]

Common Mistakes:

• Changing base image to node:8080 (invalid)
• Exposing port without changing app port
• Passing port as npm start argument without app support