Dockerized PostgreSQL and Django for Local Development

October 31, 2017 | programming | devops | databases |

Docker and docker-compose make it dead simple to avoid dependency hell and have a consistent environment for your whole team while doing local development. This post walks through setting up a new Django project from scratch to use Docker and docker-compose. It is modeled after a previous post that I wrote about doing a similar thing with Laravel and MySQL.

Dockerfile

Nothing too interesting happening here. Installing python and pip.

FROM ubuntu:16.04

system update

RUN apt update RUN apt upgrade -y

python deps

RUN apt install -y python3-dev python3-pip

docker-compose.yml

version: '2'
services:
  app:
    build: .
    ports:
      - "8000:8000"
    volumes:
      - .:/app
    working_dir: /app
    command: bash -c "pip3 install -r requirements.txt && python3 manage.py migrate && python3 manage.py runserver 0:8000"
    depends_on:
      - db
  db:
    image: postgres:9.6.5-alpine
    environment:
      - POSTGRES_USER=feedread
      - POSTGRES_PASSWORD=feedread
    volumes:
      - ./data:/var/lib/postgresql/data
    ports:
      - "5432:5432"

With this in place you can start your Django app with docker-compose up. Each time the app starts it will install the latest dependencies, run migrations, and start serving the app on localhost:8000

Notes

In order to do stuff with the database locally you should add the following record to your local /etc/hosts file
```
# /etc/hosts
127.0.0.1 db
```
Since we define - .:/app as a volume, this means that all of your local changes are immediately visible in the dockerized app.
If you need to access the running app or db container you can do so with docker-compose exec app bash or docker-compose exec db bash.
This docker-compose file is not really suitable for production since it is not likely that you would want to build the container each time the app starts or automatically run migrations.
You can add additional services like memcached, a mail server, an app server, a queue, etc., using the same method that we are using above with our database.

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Give Your Spouse the Gift of a Couple's Email Domain from mtlynch.io
Skip the Next iPhone from Articles on Jose M.
Have smart glasses finally hit an inflection point? from The Torment Nexus
The McPhee method from the jsomers.net blog
Pluralistic: LLMs are slot-machines (16 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
Pluralistic: Bluesky creates the world's weirdest, hardest-to-understand binding arbitration clause (15 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
Just a Little More Context Bro, I Promise, and It’ll Fix Everything from Jim Nielsen’s Blog
The Futzing Fraction from Deciphering Glyph

Articles from blogs I follow around the net

If you’re like me; you like files, you like web technologies like HTML, CSS, and JavaScript, you like markdown, you like kanban, you like pomodoro, and you like apps. If this sounds like you reach out. I’ll be open sourcing something in the coming weeks a…

via Colin Devroe September 3, 2025

Pluralistic: The worst possible antitrust outcome (03 Sep 2025)

Today's links The worst possible antitrust outcome: Hope you like enshittification. Hey look at this: Delights to delectate. Object permanence: Amazon drivers hang phones from trees; DVD Jon v Windows DRM; Chevron's dirty tricks. Upcoming appearan…

via Pluralistic: Daily links from Cory Doctorow September 3, 2025

Give a Problem. Grow a Programmer.

In 2009, I kicked off my senior year in college with a class that ultimately changed the way I thought about my degree—and my future.

via flower.codes September 3, 2025

Generated by openring