Docker deployment for Vue apps - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Docker used for in deploying Vue apps?

Docker packages your Vue app and its environment into a container. This makes it easy to run the app anywhere without setup issues.

beginner

What is the purpose of a Dockerfile in Vue app deployment?

A Dockerfile contains step-by-step instructions to build a Docker image for your Vue app, including installing dependencies and building the app.

intermediate

Why do we use a multi-stage build in Docker for Vue apps?

Multi-stage builds let you separate the build environment from the final image. This keeps the final image small and only includes what is needed to run the app.

beginner

What command do you run to build a Docker image for your Vue app?

You run docker build -t your-image-name . in the folder with your Dockerfile to create the image.

intermediate

How do you serve a built Vue app inside a Docker container?

After building the Vue app, you use a lightweight web server like Nginx inside the container to serve the static files.

What is the first step in deploying a Vue app with Docker?

A Run the Vue app locally

B Install Vue CLI globally

C Push code to GitHub

D Create a Dockerfile with build instructions

You start by creating a Dockerfile that tells Docker how to build your app image.

Which Docker feature helps keep the final image small when deploying Vue apps?

A Docker volumes

B Multi-stage builds

C Docker networks

D Docker Compose

Multi-stage builds separate build and runtime environments, reducing image size.

What web server is commonly used inside Docker containers to serve Vue apps?

A IIS

B Apache

C Nginx

D Tomcat

Nginx is lightweight and efficient for serving static files like built Vue apps.

Which command runs a Docker container from your Vue app image?

A docker run -p 8080:80 your-image-name

B docker build your-image-name

C vue serve your-app

D npm start

The docker run command starts the container and maps ports for access.

Why is it important to build your Vue app before serving it in Docker?

A To create optimized static files for production

B To install Vue CLI inside the container

C To run the app in development mode

D To enable hot module replacement

Building creates optimized files that load faster and work well in production.

Explain the steps to create a Docker image for a Vue app using a Dockerfile.

Think about how to prepare the app and then serve it efficiently.

Describe why Docker is helpful for deploying Vue apps and how it ensures consistency.

Imagine moving your app to a friend's computer without issues.

Practice

1. What is the main purpose of using Docker for deploying a Vue app?

easy

A. To write Vue components faster

B. To replace Vue Router in the app

C. To package the app and its environment for consistent deployment

D. To automatically generate Vue templates

Solution

1. Step 1: Understand Docker's role

   Docker packages an app with all its dependencies and environment to ensure it runs the same everywhere.

2. Step 2: Identify deployment benefits

   This packaging helps avoid issues caused by different environments on different machines.

3. Final Answer:

   To package the app and its environment for consistent deployment -> Option C

4. Quick Check:

   Docker packages environment [OK]

Hint: Docker ensures app runs same everywhere by packaging environment [OK]

Common Mistakes:

• Thinking Docker speeds up coding
• Confusing Docker with Vue features
• Assuming Docker replaces Vue libraries

2. Which Dockerfile snippet correctly uses multi-stage build for a Vue app?

easy

A. FROM node:18 AS build
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build
FROM nginx:alpine
COPY --from=build /app/dist /usr/share/nginx/html

B. FROM nginx:alpine
WORKDIR /app
COPY . .
RUN npm install
RUN npm run build

C. FROM node:18
WORKDIR /app
COPY . .
RUN npm run serve

D. FROM alpine
RUN apk add nodejs npm
COPY . .
RUN npm run build

Solution

1. Step 1: Identify multi-stage build pattern

   Multi-stage uses one stage to build (Node) and another to serve (Nginx).

2. Step 2: Check snippet correctness

   FROM node:18 AS build WORKDIR /app COPY package*.json ./ RUN npm install COPY . . RUN npm run build FROM nginx:alpine COPY --from=build /app/dist /usr/share/nginx/html builds with Node, then copies build output to Nginx image, which is correct.

3. Final Answer:

   Multi-stage build with Node for build and Nginx to serve -> Option A

4. Quick Check:

   Multi-stage build [OK]

Hint: Look for two FROM lines: build then serve [OK]

Common Mistakes:

• Using Nginx to build Vue app
• Not copying build output to Nginx
• Running npm serve inside Docker production image

3. Given this Dockerfile snippet, what will happen when you run the container?

FROM node:18 AS build
WORKDIR /app
COPY package.json .
RUN npm install
COPY . .
RUN npm run build
FROM nginx:alpine
COPY --from=build /app/dist /usr/share/nginx/html
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]

medium

A. The container will expose port 3000 instead of 80

B. The container will fail because npm run build is missing

C. The app will run Node server instead of Nginx

D. The Vue app will be built and served by Nginx on port 80

Solution

1. Step 1: Analyze build stage

   Node image installs dependencies and runs npm run build to create production files in /app/dist.

2. Step 2: Analyze serve stage

   Nginx image copies built files to its html folder and exposes port 80, running Nginx server.

3. Final Answer:

   The Vue app will be built and served by Nginx on port 80 -> Option D

4. Quick Check:

   Build then serve on port 80 [OK]

Hint: Build with Node, serve with Nginx on port 80 [OK]

Common Mistakes:

• Assuming npm run build is missing
• Confusing Node server with Nginx
• Wrong port exposed in container

4. You wrote this Dockerfile but your Vue app shows a blank page when running the container:

FROM node:18
WORKDIR /app
COPY . .
RUN npm install
RUN npm run build
FROM nginx:alpine
COPY dist /usr/share/nginx/html
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]

What is the likely error?

medium

A. Nginx image does not expose port 80

B. Missing multi-stage build alias causing wrong files copied

C. npm install command is incorrect

D. CMD syntax is invalid

Solution

1. Step 1: Check multi-stage build usage

   The Dockerfile lacks a build stage alias, so COPY dist copies from current stage, which is Nginx, not build output.

2. Step 2: Understand impact on app

   Because dist folder is not copied from build stage, Nginx serves empty or missing files, causing blank page.

3. Final Answer:

   Missing multi-stage build alias causing wrong files copied -> Option B

4. Quick Check:

   Missing build alias = blank page [OK]

Hint: Use --from=build to copy correct build files [OK]

Common Mistakes:

• Ignoring multi-stage build alias
• Assuming port exposure causes blank page
• Thinking npm install syntax is wrong

5. You want to optimize your Vue app Docker deployment by reducing image size and improving build speed. Which approach is best?

hard

A. Use a multi-stage Dockerfile with Node build stage and minimal Nginx serve stage

B. Install all dependencies in the Nginx image directly

C. Run npm run serve inside the Node image and expose port 8080

D. Copy source files directly to Nginx image and run npm build there

Solution

1. Step 1: Understand image size and build speed

   Multi-stage builds separate build environment from runtime, keeping final image small and clean.

2. Step 2: Evaluate options

   Use a multi-stage Dockerfile with Node build stage and minimal Nginx serve stage uses Node only for building, then copies only built files to lightweight Nginx image, optimizing size and speed.

3. Final Answer:

   Use a multi-stage Dockerfile with Node build stage and minimal Nginx serve stage -> Option A

4. Quick Check:

   Multi-stage build optimizes size and speed [OK]

Hint: Separate build and serve stages to keep image small [OK]

Common Mistakes:

• Installing dependencies in Nginx image
• Running dev server in production container
• Copying source files without building