Docker containerization in ML Python

Introduction

Docker helps package your machine learning code and all its parts so it runs the same everywhere. This makes sharing and running models easy and reliable.

You want to share your ML model with a teammate who uses a different computer setup.

You need to run your ML training on a cloud server without worrying about missing software.

You want to keep your ML project organized with all dependencies in one place.

You want to test your ML model in different environments without changing your main system.

You want to deploy your ML model as a service that others can access easily.

Syntax

ML Python

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

FROM sets the base image with Python installed.

WORKDIR sets the folder inside the container where commands run.

Examples

Basic Dockerfile to run a Python ML training script with dependencies.

ML Python

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

Dockerfile using TensorFlow image to serve a trained model.

ML Python

FROM tensorflow/tensorflow:latest
WORKDIR /model
COPY . .
CMD ["python", "serve_model.py"]

Dockerfile installing specific ML libraries for prediction script.

ML Python

FROM python:3.12
WORKDIR /app
COPY . .
RUN pip install scikit-learn pandas
CMD ["python", "predict.py"]

Sample Model

This simple Python script trains a linear model and predicts output for input 6. You can put this script in a Docker container to run anywhere with the same result.

ML Python

import numpy as np
from sklearn.linear_model import LinearRegression

# Sample data
X = np.array([[1], [2], [3], [4], [5]])
y = np.array([2, 4, 6, 8, 10])

# Train model
model = LinearRegression()
model.fit(X, y)

# Predict
pred = model.predict(np.array([[6]]))
print(f"Prediction for input 6: {pred[0]:.2f}")

Important Notes

Always include a requirements.txt file listing your Python packages for easy installation inside Docker.

Keep your Docker images small by using slim or minimal base images.

Test your container locally before deploying to cloud or sharing.

Summary

Docker packages your ML code and environment together for easy sharing and running.

Use Dockerfiles to specify how to build your ML container step-by-step.

Running ML code in Docker ensures consistent results on any machine.

Practice

1. What is the main benefit of using Docker for machine learning projects?

easy

A. It replaces the need for training data

B. It automatically improves model accuracy

C. It packages code and environment together for consistent runs

D. It speeds up GPU computations directly

Solution

1. Step 1: Understand Docker's purpose

   Docker bundles your ML code with all software and libraries needed.

2. Step 2: Identify the benefit for ML projects

   This bundling ensures your code runs the same on any machine, avoiding environment issues.

3. Final Answer:

   It packages code and environment together for consistent runs -> Option C

4. Quick Check:

   Docker = consistent environment [OK]

Hint: Docker bundles code + environment for consistency [OK]

Common Mistakes:

• Thinking Docker improves model accuracy
• Believing Docker replaces training data
• Assuming Docker speeds up hardware directly

2. Which of the following is the correct syntax to start a Docker container named ml_container from an image called ml_image?

easy

A. docker build ml_container ml_image

B. docker start ml_image --name ml_container

C. docker create ml_container ml_image

D. docker run --name ml_container ml_image

Solution

1. Step 1: Recall Docker run command usage

   The docker run command starts a container from an image and can assign a name with --name.

2. Step 2: Check each option

   docker run --name ml_container ml_image correctly uses docker run --name container image. Others misuse commands: start needs container ID, create creates but doesn't start, build builds images.

3. Final Answer:

   docker run --name ml_container ml_image -> Option D

4. Quick Check:

   docker run + --name = start container [OK]

Hint: Use 'docker run --name container image' to start named container [OK]

Common Mistakes:

• Using 'docker start' with image name instead of container
• Confusing 'docker create' with 'docker run'
• Using 'docker build' to start containers

3. Given this Dockerfile snippet for an ML project:

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

What happens when you build and run this container?

medium

A. It only copies files but does not install dependencies

B. It installs dependencies and runs train.py inside the container

C. It runs train.py on the host machine, not inside container

D. It fails because CMD syntax is incorrect

Solution

1. Step 1: Analyze Dockerfile commands

   The Dockerfile uses FROM python:3.8-slim to get Python, sets working directory, copies requirements, installs them, copies code, then runs train.py.

2. Step 2: Understand container build and run

   Building creates an image with dependencies installed. Running executes python train.py inside the container environment.

3. Final Answer:

   It installs dependencies and runs train.py inside the container -> Option B

4. Quick Check:

   Dockerfile installs + runs script inside container [OK]

Hint: Dockerfile RUN installs, CMD runs script inside container [OK]

Common Mistakes:

• Thinking dependencies install on host, not container
• Believing CMD runs outside container
• Assuming CMD syntax is invalid here

4. You wrote a Dockerfile but when building the image, you get an error: ERROR: Could not open requirements.txt. What is the most likely cause?

medium

A. requirements.txt is not in the build context directory

B. Python version in FROM is too old

C. CMD syntax is wrong

D. Docker daemon is not running

Solution

1. Step 1: Understand build context and COPY command

   The COPY command copies files from the build context (folder where docker build runs). If requirements.txt is missing there, COPY fails.

2. Step 2: Check error cause

   Error says requirements.txt can't be opened, so likely it's not in the folder where build runs, causing failure.

3. Final Answer:

   requirements.txt is not in the build context directory -> Option A

4. Quick Check:

   Missing file in build context = COPY error [OK]

Hint: Ensure files are in build folder before docker build [OK]

Common Mistakes:

• Blaming Python version for file not found
• Assuming CMD syntax causes file errors
• Not checking if Docker daemon is running

5. You want to share your ML model training environment with a teammate. Which Docker approach ensures they get the exact same setup including Python version, libraries, and your training script?

hard

A. Create a Dockerfile specifying Python version, dependencies, and copy training code

B. Send them your Python script and ask them to install dependencies manually

C. Use a virtual environment on your machine and share it via email

D. Only share the trained model file without environment details

Solution

1. Step 1: Identify how to package environment and code

   A Dockerfile lets you specify exact Python version, libraries, and copies your code, creating a reproducible image.

2. Step 2: Compare options for sharing environment

   Manual installs or virtual envs are error-prone and not portable. Sharing only model misses environment needed for training.

3. Final Answer:

   Create a Dockerfile specifying Python version, dependencies, and copy training code -> Option A

4. Quick Check:

   Dockerfile = reproducible ML environment [OK]

Hint: Use Dockerfile to share full ML environment [OK]

Common Mistakes:

• Thinking manual installs guarantee same environment
• Believing virtualenv can be emailed and run anywhere
• Ignoring environment when sharing model files