Docker containerization in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Docker containerization?

Docker containerization is a way to package an application and all its parts into a single container. This container can run anywhere, making the app easy to share and deploy.

beginner

Why use Docker with a Flask app?

Using Docker with Flask helps keep the app environment consistent. It ensures the app runs the same on your computer, a server, or in the cloud, avoiding "it works on my machine" problems.

intermediate

What is a Dockerfile in the context of Flask?

A Dockerfile is a simple text file with instructions to build a Docker image. For Flask, it usually tells Docker which Python version to use, copies your app code, installs dependencies, and sets how to start the app.

beginner

How does Docker help with dependencies in Flask projects?

Docker packages all dependencies inside the container. This means you don't need to install Python or libraries on your computer separately; the container has everything your Flask app needs.

intermediate

What is the difference between a Docker image and a Docker container?

A Docker image is like a recipe or blueprint for your app. A Docker container is the running instance of that image, like a cake made from the recipe.

What file do you use to define how to build a Docker image for a Flask app?

A Dockerfile

B requirements.txt

C app.py

D docker-compose.yml

The Dockerfile contains instructions to build the Docker image, including setting up the environment and copying your Flask app.

Which command runs a Docker container from an image?

A docker build

B docker pull

C docker push

D docker run

The 'docker run' command starts a container from a Docker image.

Why is containerization useful for Flask apps?

A It makes the app run faster on all computers

B It packages the app with its environment so it runs the same everywhere

C It automatically writes Flask code

D It replaces the need for Python

Containerization packages the app and its environment, ensuring consistent behavior across different machines.

What does the 'EXPOSE' instruction in a Dockerfile do?

A Specifies which port the container listens on

B Runs the Flask app

C Copies files into the container

D Installs dependencies

'EXPOSE' tells Docker which port the container will listen on for network connections.

Which of these is NOT a benefit of using Docker with Flask?

A Consistent environment across machines

B Simplifies deployment

C Automatically fixes bugs in Flask code

D Packages dependencies inside the container

Docker does not fix bugs in your code; it helps with environment consistency and deployment.

Explain how Docker containerization helps when deploying a Flask application.

Think about how Docker solves the 'works on my machine' problem.

Describe the role of a Dockerfile in creating a Docker container for a Flask app.

It's like a recipe for building your app's container.

Practice

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

easy

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

B. To write Flask application code faster

C. To replace Flask's routing system

D. To automatically generate HTML templates

Solution

1. Step 1: Understand Docker's role

   Docker packages an app with all its dependencies into a container.

2. Step 2: Connect Docker to Flask app usage

   This packaging ensures the Flask app runs the same on any machine without setup issues.

3. Final Answer:

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

4. Quick Check:

   Docker packages app + environment = B [OK]

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

Common Mistakes:

• Thinking Docker speeds up coding
• Confusing Docker with Flask features
• Assuming Docker changes app logic

2. Which of the following is the correct first line in a Dockerfile for a Flask app using Python 3.12?

easy

A. EXPOSE 5000

B. RUN python3.12 install flask

C. COPY app.py /app

D. FROM python:3.12-slim

Solution

1. Step 1: Identify Dockerfile base image syntax

   The Dockerfile must start with a FROM statement specifying the base image.

2. Step 2: Choose correct Python version image

   "FROM python:3.12-slim" correctly sets Python 3.12 as base.

3. Final Answer:

   FROM python:3.12-slim -> Option D

4. Quick Check:

   Dockerfile starts with FROM base image = D [OK]

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

Common Mistakes:

• Using RUN before FROM
• Copying files before setting base image
• Exposing ports before base image

3. Given this Dockerfile snippet for a Flask app:

FROM python:3.12-slim
WORKDIR /app
COPY requirements.txt ./
RUN pip install -r requirements.txt
COPY . .
CMD ["python", "app.py"]

What happens when you run docker build . and then docker run?

medium

A. The app fails because requirements.txt is not copied

B. The Flask app runs inside a container using Python 3.12 with dependencies installed

C. The container runs but does not start the Flask app

D. The build command installs Flask globally on the host machine

Solution

1. Step 1: Analyze Dockerfile commands

   It sets Python 3.12 base, copies requirements.txt, installs dependencies, copies app files, and runs app.py.

2. Step 2: Understand build and run effects

   docker build creates image with dependencies; docker run starts container running Flask app.

3. Final Answer:

   The Flask app runs inside a container using Python 3.12 with dependencies installed -> Option B

4. Quick Check:

   Build installs deps, run starts app = A [OK]

Hint: COPY then RUN pip install ensures dependencies inside container [OK]

Common Mistakes:

• Thinking dependencies install on host
• Assuming app.py is not copied
• Believing container runs without CMD

4. You wrote this Dockerfile for your Flask app:

FROM python:3.12-slim
COPY app.py /app/
CMD ["python", "app.py"]

When you run the container, the app crashes with "ModuleNotFoundError: flask". What is the problem?

medium

A. Flask is not installed inside the container

B. app.py is not copied to the container

C. CMD syntax is incorrect

D. Python version 3.12-slim does not support Flask

Solution

1. Step 1: Check Dockerfile for dependency installation

   No RUN command installs Flask or dependencies inside container.

2. Step 2: Understand error cause

   ModuleNotFoundError means Flask package missing in container environment.

3. Final Answer:

   Flask is not installed inside the container -> Option A

4. Quick Check:

   Missing Flask install causes ModuleNotFoundError = C [OK]

Hint: Always RUN pip install for dependencies inside Dockerfile [OK]

Common Mistakes:

• Assuming Flask is preinstalled in base image
• Thinking app.py copy is missing
• Believing CMD syntax causes import errors

5. You want to containerize a Flask app that reads environment variables for configuration. Which Dockerfile addition ensures environment variables set at runtime are accessible inside the Flask app?

hard

A. Hardcode variables inside app.py before building image

B. Use ENV in Dockerfile to set variables permanently

C. Pass variables with docker run -e VAR=value and access via os.environ in Flask

D. Add EXPOSE for environment variables

Solution

1. Step 1: Understand environment variable usage

   Flask app reads variables at runtime from OS environment.

2. Step 2: Identify Docker method to pass runtime variables

   Using docker run -e VAR=value passes variables dynamically to container.

3. Final Answer:

   Pass variables with docker run -e VAR=value and access via os.environ in Flask -> Option C

4. Quick Check:

   Runtime env vars via docker run -e = A [OK]

Hint: Use docker run -e to pass env vars dynamically to container [OK]

Common Mistakes:

• Confusing ENV for runtime variable passing
• Hardcoding vars loses flexibility
• Thinking EXPOSE relates to env vars