Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      In-House vs. Outsource Node.js Development Teams: 9 Key Differences for the C-Suite (2025)

      July 19, 2025

      Why Non-Native Content Designers Improve Global UX

      July 18, 2025

      DevOps won’t scale without platform engineering and here’s why your teams are still stuck

      July 18, 2025

      This week in AI dev tools: Slack’s enterprise search, Claude Code’s analytics dashboard, and more (July 18, 2025)

      July 18, 2025

      DistroWatch Weekly, Issue 1131

      July 20, 2025

      I ditched my Bluetooth speakers for this slick turntable – and it’s more practical than I thought

      July 19, 2025

      This split keyboard offers deep customization – if you’re willing to go all in

      July 19, 2025

      I spoke with an AI version of myself, thanks to Hume’s free tool – how to try it

      July 19, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      The details of TC39’s last meeting

      July 20, 2025
      Recent

      The details of TC39’s last meeting

      July 20, 2025

      Simple wrapper for Chrome’s built-in local LLM (Gemini Nano)

      July 19, 2025

      Online Examination System using PHP and MySQL

      July 18, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      Windows 11 tests “shared audio” to play music via multiple devices, new taskbar animations

      July 20, 2025
      Recent

      Windows 11 tests “shared audio” to play music via multiple devices, new taskbar animations

      July 20, 2025

      WhatsApp for Windows 11 is switching back to Chromium web wrapper from UWP/native

      July 20, 2025

      DistroWatch Weekly, Issue 1131

      July 20, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Development»How to Dockerize Your Django Project

    How to Dockerize Your Django Project

    April 18, 2025

    If you’re working on a Django project and you want to make your life easier – especially when it comes to running your app across different environments – Docker is your new best friend.

    Docker makes it possible to package your Django app, along with all its dependencies, into something called a “container.”

    That way, it runs the same on your computer, your teammate’s computer, a testing server, or even in production.

    When I first started using Docker, it felt a little overwhelming. But after setting it up for a few Django apps, it all clicked.

    The good news? I’m going to walk you through it, step by step, in a way that’s easy to follow, even if you’re brand new to Docker.

    Table of Contents

    1. What You’ll Need

    2. How to Dockerize Your Django Project

      • Step 1: Start a Django Project

      • Step 2: Create a Dockerfile

      • Step 3: Add a requirements.txt

      • Step 4: Create docker-compose.yml

      • Step 5: Run It!

    3. Common Issues

      • Port Already in Use?

      • Database Not Working?

    4. FAQs

      • Do I need Docker for development?

      • Can I run migrations inside Docker?

      • How do I stop everything?

    5. Extra Tip: Use .dockerignore

    6. What You’ve Built

    7. Want to Go Deeper?

    8. Further Reading

    What You’ll Need

    Before we begin, make sure you’ve got a few things installed:

    • Python 3 (any version that Django supports)

    • Django (of course)

    • Docker and Docker Compose
      👉 Install Docker
      👉 Install Docker Compose

    You don’t need to be an expert in Docker. I’ll explain what each part does as we build it together.

    How to Dockerize Your Django Project

    Step 1: Start a Django Project

    If you already have a Django project, you can skip this part.

    Otherwise, open your terminal and run:

    django-admin startproject myproject
    cd myproject
    

    This will create a new Django project called myproject. You’ll see a structure like this:

    myproject/
    ├── manage.py
    └── myproject/
        ├── __init__.py
        ├── asgi.py
        ├── settings.py
        ├── urls.py
        └── wsgi.py
    

    Let’s say this is your app that you want to run inside Docker.

    Step 2: Create a Dockerfile

    In the root of your project (same folder as manage.py), create a file called Dockerfile. No file extension –just Dockerfile.

    Here’s what goes inside:

    # Use the official Python image
    FROM python:3.10-slim
    
    # Set environment variables
    ENV PYTHONDONTWRITEBYTECODE=1
    ENV PYTHONUNBUFFERED=1
    
    # Set the working directory in the container
    WORKDIR /app
    
    # Install dependencies
    COPY requirements.txt /app/
    RUN pip install --upgrade pip && pip install -r requirements.txt
    
    # Copy the rest of the code
    COPY . /app/
    

    Let me break that down:

    • FROM python:3.10-slim: This tells Docker to use a lightweight version of Python 3.10.

    • ENV: These just help with cleaner logs and better performance.

    • WORKDIR /app: This sets the default working directory inside the container.

    • COPY and RUN: These lines copy your code into the container and install your Python packages.

    Step 3: Add a requirements.txt

    You’ll need a file listing your Python packages.

    Create a file called requirements.txt in the root folder and add:

    Django>=4.0,<5.0
    

    You can add more later if your project grows. For now, that’s enough.

    To generate a full list of dependencies from your local virtual environment, run:

    pip freeze > requirements.txt
    

    Step 4: Create docker-compose.yml

    Now let’s create the file that tells Docker how to run everything together.

    In your root folder, create docker-compose.yml:

    version: '3.9'
    
    services:
      web:
        build: .
        command: python manage.py runserver 0.0.0.0:8000
        volumes:
          - .:/app
        ports:
          - "8000:8000"
    

    Let’s go line-by-line:

    • build: .: This tells Docker to use the Dockerfile in the current folder.

    • command: This runs Django’s development server inside the container.

    • volumes: This mounts your code into the container so changes are reflected live.

    • ports: This maps port 8000 inside Docker to port 8000 on your machine.

    So if you go to http://localhost:8000, you’ll see your app.

    Step 5: Run It!

    Now the fun part. From your terminal, run:

    docker-compose up --build
    

    This tells Docker to:

    • Build the container

    • Install dependencies

    • Run the Django server

    If everything goes well, you’ll see logs from the Django server, and you can open your browser and go to http://localhost:8000.

    You should see the Django welcome screen.

    Common Issues

    Port Already in Use?

    If port 8000 is busy, change this line in docker-compose.yml:

    ports:
      - "8001:8000"
    

    Then go to http://localhost:8001.

    Database Not Working?

    If you need a database (like PostgreSQL), you can add another service to docker-compose.yml. Here’s an example with PostgreSQL:

    services:
      db:
        image: postgres
        environment:
          POSTGRES_DB: mydb
          POSTGRES_USER: user
          POSTGRES_PASSWORD: password
      web:
        build: .
        command: python manage.py runserver 0.0.0.0:8000
        volumes:
          - .:/app
        ports:
          - "8000:8000"
        depends_on:
          - db
    

    Then, update your settings.py in Django to use that database.

    FAQs

    Do I need Docker for development?

    No, but it helps keep your environment clean and consistent. If it works in Docker, it’ll work anywhere.

    Can I run migrations inside Docker?

    Yes! Just run:

    docker-compose run web python manage.py migrate
    

    How do I stop everything?

    Press Ctrl+C to stop the running server, and if you want to remove containers:

    docker-compose down
    

    Extra Tip: Use .dockerignore

    Just like .gitignore, you can create a .dockerignore file to avoid copying unnecessary files into the Docker container. Here’s a simple one:

    __pycache__
    *.pyc
    *.pyo
    *.pyd
    .env
    .git
    

    What You’ve Built

    By now, you’ve:

    • Created a Django project

    • Built a Docker container for it

    • Set up docker-compose to run everything

    • Learned how to manage it all easily

    Once you’re comfortable, you can expand this setup with static files, NGINX, Gunicorn, or even production-ready Docker builds.

    Want to Go Deeper?

    If this feels like a lot, that’s ok. It takes a little practice, but once you’ve done it a few times, Docker becomes second nature.

    You’ll spend less time debugging setup issues and more time coding your app.

    Further Reading

    • Docker Documentation

    • Django Official Docs

    • Compose File Reference

    Source: freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More 

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleThink GeoGuessr is fun? Try using ChatGPT to guess locations in your photos
    Next Article How to Use Celery in Django

    Related Posts

    Artificial Intelligence

    Scaling Up Reinforcement Learning for Traffic Smoothing: A 100-AV Highway Deployment

    July 20, 2025
    Repurposing Protein Folding Models for Generation with Latent Diffusion
    Artificial Intelligence

    Repurposing Protein Folding Models for Generation with Latent Diffusion

    July 20, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    What are haptic touchpads? Here’s how they work in Windows laptops and why you should want them in other devices

    News & Updates

    Krutik Poojara | Cybersecurity Expert, AI Researcher & Author

    Web Development

    CISA Adds Four Critical Vulnerabilities to KEV Catalog Due to Active Exploitation

    Security

    Valve reveals new SteamOS Compatibility system for Non-Steam Decks like Legion Go S SteamOS — 18,000+ titles expected “out of the gate”

    News & Updates

    Highlights

    Privilege Escalation Flaw in IBM Backup Services Threatens IBM i Environments (CVE-2025-33108)

    June 15, 2025

    Privilege Escalation Flaw in IBM Backup Services Threatens IBM i Environments (CVE-2025-33108)

    IBM has disclosed a high-severity vulnerability affecting its Backup, Recovery, and Media Services (BRMS) for IBM i systems, specifically versions 7.5 and 7.4. Identified as CVE-2025-33108, this flaw …
    Read more

    Published Date:
    Jun 16, 2025 (1 hour, 54 minutes ago)

    Vulnerabilities has been mentioned in this article.

    CVE-2025-33108

    CVE-2025-27453 – Apache PHP HttpOnly Cookie Access Vulnerability

    July 3, 2025

    CVE-2023-28902 – Skoda MIB3 Infotainment Unit Integer Underflow Denial-of-Service Vulnerability

    June 28, 2025

    CVE-2025-28382 – OpenC3 COSMOS Directory Traversal Vulnerability

    June 13, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.