Good Introduction Docker For Python Developers

Photo by writer | Ideogram

Obvious Introduction

You just forced your Python app production, and suddenly everything breaks. The app worked well on your laptop, passing all the exercises to CI, but now dropped mysterious mistakes in production. Sounds normal? Or maybe you're facing a new engineer spending just three days trying to find your project in your area. The Windows, upgrade to Mac, a manufacturer server works humanity, and somehow everyone has different Python translations and conflicting package.

We all are there, it is difficult to abuse the abuse – the construction of the construction of the construction factors. Designer Solving this confusion by installing all the nature of your request in a container that works everywhere. No more “works on my machine” excuse. No more are used on weekends made to correct an error. This article will import you to pull and how to use a docker to facilitate app development. You will also read how to comment on the simple Python app using the Docker.

🔗 Link to the code in Githubub

Obvious How Docker works and why you need it

Think of Docker as analogous in shipping containers, but with your code. When the Python App system appears, you cannot pack your code. Puts all the nature of the time of running: some type of Python, all your dependence, libraries, environmental variables, and app for your expected app.

The result? Your app works the same way on your laptop, a team of workmeeter, milling server, and production. Every time. But how did you do that?

Yes, when contains Python apps with Docker, you do the following. You enter your application into a portable artifact called “Photo”. After that, you start “containers” – practical conditions of images – and then run your apps in the content.

Obvious Creating a Python Web API

Instead of starting the toy examples, let's start the actual python app. We will build a simple Fastapi-Based Todo API (with Vicorn Like an asgi server) showing patterns to use in real projects, and use The Widiles with data verification.

Attention to your project, create a requirement file.txt:

fastapi==0.116.1
uvicorn[standard]==0.35.0
pydantic==2.11.7

Now let's build a basic app structure:

# app.py
from fastapi import FastAPI
from pydantic import BaseModel
from typing import List
import os

app = FastAPI(title="Todo API")
todos = []
next_id = 1

Enter data models:

class TodoCreate(BaseModel):
    title: str
    completed: bool = False

class Todo(BaseModel):
    id: int
    title: str
    completed: bool

Create an ending to test health:

@app.get("
def health_check():
    return {
        "status": "healthy",
        "environment": os.getenv("ENVIRONMENT", "development"),
        "python_version": os.getenv("PYTHON_VERSION", "unknown")
    }

Enter Todo Todo performance:

@app.get("/todos", response_model=List[Todo])
def list_todos():
    return todos

@app.post("/todos", response_model=Todo)
def create_todo(todo_data: TodoCreate):
    global next_id
    new_todo = Todo(
        id=next_id,
        title=todo_data.title,
        completed=todo_data.completed
    )
    todos.append(new_todo)
    next_id += 1
    return new_todo

@app.delete("/todos/{todo_id}")
def delete_todo(todo_id: int):
    global todos
    todos = [t for t in todos if t.id != todo_id]
    return {"message": "Todo deleted"}

Finally, add the server startup code:

if __name__ == "__main__":
    import uvicorn
    uvicorn.run(app, host="0.0.0.0", port=8000)

If you run this in your area pip install -r requirements.txt && python app.pyYou will have API running in your area. Let us now continue the request.

Obvious To write your first dockerfile

You have your application, you have a list of needs, and the specific place of your application to run. So how do you go to these distinctive items in one docker picture containing your code and depending on? You can specify this by writing a dockerfile about your request.

Think about it as a cooking method from different parts of your project. Create Dockfile in your project directory (no extension).

# Start with a base Python image:
FROM python:3.11-slim

# Set environment variables:
ENV PYTHONDONTWRITEBYTECODE=1 
    PYTHONUNBUFFERED=1 
    ENVIRONMENT=production 
    PYTHON_VERSION=3.11

# Set up the working directory:
WORKDIR /app

# Install dependencies (this order is important for caching):
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

# Copy your application code:
COPY . .

# Expose the port and set the startup command:
EXPOSE 8000
CMD ["python", "app.py"]

This Docpiller forms a container of the Python Web site. Using Picture of Python 3.11 (Slim Version) As a valid basis, we enter a valid directory, to enter the delivery of service.txt, college code code, and works the app python app.py. The building follows good habits by leaning before copying the code to use Docker's Savings Latest.

Obvious To build and use your first bowl

Now let's build and use our leading app:

# Build the Docker image
docker build -t my-todo-app .

# Run the container
docker run -p 8000:8000 my-todo-app

When you run docker buildYou will see that each line in your dockerfile field is designed as a layer. The first construction can take a bit as a docker downloads the Python picture and includes your dependence.

⚠️ Use docker buildx build To create a photo from Dockefile commands using the building.

This page -t my-todo-app Flag Tags your photo with better name instead of random hash. This page -p 8000:8000 Part Maps Port 8000 within a bowl to Port 8000 on your catch machine.

You can visit To see that your API works within a container. The same bowl will apply for suspension from any docker machine.

Obvious Important Community Docker Instructions for Daily Use

Here is Docker instructions to use most:

# Build an image
docker build -t myapp .

# Run a container in the background
docker run -d -p 8000:8000 --name myapp-container myapp

# View running containers
docker ps

# View container logs
docker logs myapp-container

# Get a shell inside a running container
docker exec -it myapp-container /bin/sh

# Stop and remove containers
docker stop myapp-container
docker rm myapp-container

# Clean up unused containers, networks, images
docker system prune

Obvious Some of the best habits are important

After working with Docker in production, here is practices that make the difference.

Regularly use certain Version Version tags for the foundations:

# Instead of this
FROM python:3.11

# Use this
FROM python:3.11.7-slim

Create a .Dockerignore file to remove unnecessary files:

__pycache__
*.pyc
.git
.pytest_cache
node_modules
.venv
.env
README.md

Keep your photos based on cleaning package cleaners:

RUN apt-get update && apt-get install -y --no-install-recommends 
    build-essential 
    && rm -rf /var/lib/apt/lists/*

Stay running containers as non-root users in production.

Obvious Rolling up

This study covered the foundations, but Docker's nature is great. Here are the following places to check. By sending production, read about the first platforms of the containers such as Bernes or cloud-related services are similar AWS Direct Service Service (ECS), Google Cloud Runor Azure Conditions in Chicks.

Examine Docker security features, including confidentiality, image scan, and the blunt docker. Learn about doing well for speedy construction docker and small size. Set default default pipes and post using continuous combination / continuous delivery (CI / CD) programs such as GitUB actions including Gitlab ci.

Happy learning!

Count Priya c He is the writer and a technical writer from India. He likes to work in mathematical communication, data science and content creation. His areas of interest and professionals includes deliefs, data science and natural language. She enjoys reading, writing, codes, and coffee! Currently, he works by reading and sharing his knowledge and engineering society by disciples of teaching, how they guide, pieces of ideas, and more. Calculate and create views of the resources and instruction of codes.