Files
coder/docs/admin/templates/managing-templates/envbuilder.md
T
Mathias Fredriksson 97bc7eb9e5 docs: restructure dev container documentation (#21157)
Dev container admin docs were scattered across two locations: the Docker-based
integration under extending-templates/ and Envbuilder under managing-templates/.
There was no landing page explaining that two approaches exist or helping admins
choose between them.

This moves everything under admin/integrations/devcontainers/ with a decision
guide at the top. Dev containers are an integration with the dev container
specification, so integrations/ is a natural fit alongside JFrog, Vault, etc.

Stub pages remain at the original locations for discoverability.

New structure:

  admin/integrations/devcontainers/
  ├── index.md                                # Landing page + decision guide
  ├── integration.md                          # Docker-based dev containers
  └── envbuilder/
      ├── index.md
      ├── add-envbuilder.md
      ├── envbuilder-security-caching.md
      └── envbuilder-releases-known-issues.md

Refs #21080
2025-12-09 13:03:02 +02:00

606 B

Envbuilder

Envbuilder shifts environment definition from template administrators to developers. Instead of baking tools into template images, developers define their environments via devcontainer.json files in their repositories.

Envbuilder transforms the workspace image itself from a dev container configuration, without requiring a Docker daemon.

For setup instructions, see Envbuilder documentation.

For an alternative that uses Docker inside workspaces, see Dev Containers Integration.