How to Use Docker for Development: A Practical Guide

Docker simplifies development by packaging your app and its dependencies into isolated containers. This ensures consistency across your local machine, teammate’s setup, and production servers. Instead of manually installing databases, runtimes, or system tools, you define everything in a Dockerfile and docker-compose.yml. Here’s how to get started.

1. Set Up Your Docker Environment

Install Docker Desktop for your OS. Verify with docker --version. Then create a project folder and add a Dockerfile that describes your app’s base image, dependencies, and start command. For a Node.js app, it might look like:

  • FROM node:18-alpine
  • WORKDIR /app
  • COPY package*.json ./
  • RUN npm install
  • COPY . .
  • CMD ["npm", "start"]

Article illustration

2. Use Docker Compose for Multi‑Service Apps

Most development projects need more than one service (e.g., app + database). Create a docker-compose.yml file in the root directory. Define each service under services:. Example for a Node app with MongoDB:

  • services:
  • app: – builds from your Dockerfile, maps port 3000, mounts code as a volume for live reload.
  • db: – uses mongo:6, maps port 27017, sets environment variables.

Run docker-compose up to start everything. Changes to your source code reflect instantly thanks to volumes.

3. Leverage Volumes and Hot Reloading

Volumes synchronize your local code into the container so you can edit files without rebuilding. Add a volume under your service definition: volumes: - .:/app. This maps the current directory to /app in the container. Pair it with a dev server (like nodemon) so containers restart automatically on file changes.

4. Manage Dependencies and Environment

Use Docker’s .env file for secrets and configuration. Define variables in docker-compose.yml under env_file. For database URLs, API keys, or port overrides, this keeps your code portable. Never commit .env to version control – add it to .gitignore.

Conclusion: Docker removes “it works on my machine” frustrations. Start with a simple Dockerfile, extend with Compose for multiple services, and use volumes for live development. Once you master these basics, you can easily add testing, CI/CD pipelines, and production deployments. Try it on your next project – the learning curve pays off quickly.

sarah antaboga
Author: sarah antaboga

Leave a Reply

Your email address will not be published. Required fields are marked *