Reformats the setup and integrations docs under `docs/admin/setup` and `docs/admin/integrations` to one sentence per line, as the [docs style guide](https://github.com/coder/coder/blob/main/docs/.style/style-guide/formatting.md#one-sentence-per-line) requires. Hard-wrapped paragraphs are unwrapped and lines holding several sentences are split, so a later edit to one sentence shows up as a one-line diff. Apart from the exception below, only whitespace inside paragraphs and list items changes, and the rendered pages are the same. Comparing the changed files against `main` word for word, ignoring whitespace and blockquote `>` markers, finds differences only on the reworded lines. `git diff --word-diff` is easier to read than the line diff. 1 lines that already contained an em or en dash were reworded by hand, because `lint/emdash` treats every reflowed line as newly added. Each uses a parenthetical, a separate sentence, or a colon after a lead-in. Dashes on lines the reflow did not touch are left alone. Applied with an in-progress formatter, limited to pages listed in `docs/manifest.json` and excluding generated reference docs. This is one of a batch of PRs that split the docs by area (25 files changed, 380 insertions(+), 572 deletions(-)). --- 🤖 Built with AI assistance.
1.9 KiB
title
| title |
|---|
| Dev Containers |
Dev containers allow developers to define their development environment as code using the Dev Container specification.
Configuration lives in a devcontainer.json file alongside source code, enabling consistent, reproducible environments.
By adopting dev containers, organizations can:
- Standardize environments: Eliminate "works on my machine" issues while still allowing developers to customize their tools within approved boundaries.
- Scale efficiently: Let developers maintain their own environment definitions, reducing the burden on platform teams.
- Improve security: Use hardened base images and controlled package registries to enforce security policies while enabling developer self-service.
Coder supports two approaches for running dev containers. Choose based on your infrastructure and workflow requirements.
Dev Containers Integration
The Dev Containers Integration uses the standard @devcontainers/cli and Docker to run containers inside your workspace.
This is the recommended approach for most use cases.
Best for:
- Workspaces with Docker available (Docker-in-Docker or mounted socket)
- Dev container management in the Coder dashboard (discovery, status, rebuild)
- Multiple dev containers per workspace
Configure Dev Containers Integration
For user documentation, see the Dev Containers user guide.
Envbuilder
Envbuilder transforms the workspace image itself from a devcontainer.json, rather than running containers inside the workspace.
It does not require a Docker daemon.
Best for:
- Environments where Docker is unavailable or restricted
- Infrastructure-level control over image builds, caching, and security scanning
- Kubernetes-native deployments without privileged containers