Dev containers: reproducible development environments for your team

Development containers let you define your development environment as code. With dev containers, every developer on your team gets the same tools, runtimes, and configurations. This eliminates "works on my machine" problems and reduces onboarding time.

A dev container is defined by a .devcontainer directory in your repository. It contains a Dockerfile or docker-compose.yml that defines the environment, plus a devcontainer.json that configures VS Code or other editor settings. The container includes your language runtime, database, and development tools.

The benefits are immediate for new team members. Instead of spending a day setting up their development environment, they clone the repo and open it in VS Code. The container automatically builds with everything they need. Onboarding that took days takes hours.

Consistency across the team prevents environment-related bugs. A developer on macOS and a developer on Windows run the same container with the same Node.js version, same Python packages, and same database version. Configuration drift between environments disappears entirely.

Include development tools in your container. Add linters, formatters, and testing tools. Pin versions so everyone uses the same tools. Configure editor extensions through the devcontainer.json so VS Code automatically installs them. This standardizes the development experience.

Database and service dependencies can be included in a docker-compose.yml alongside your dev container. A single "Reopen in Container" command starts your application, database, and any other services. This replaces the complex setup instructions that usually involve installing multiple services.

Dev containers work with GitHub Codespaces for remote development. A developer can open your repository in a browser-based VS Code environment with the full dev container. This is especially useful for reviewers, designers, and other collaborators who don't want to set up a local environment.

Start with a basic dev container that includes your language runtime and essential tools. Add complexity as needed. The goal is to reduce friction, not to create a perfect environment from day one. Iterate based on team feedback.

-

Rizwan Saleem | https://rizwansaleem.co