don't encourage envbuilder

EdwardAngert · EdwardAngert · commit 0b5cd2487fb8 · 2025-07-09T05:34:32.000Z
diff --git a/docs/admin/templates/managing-templates/devcontainers/add-devcontainer.md b/docs/admin/templates/managing-templates/devcontainers/add-devcontainer.md
@@ -6,6 +6,8 @@ This allows the template to prompt for the developer for their dev container rep
 [parameter](../../extending-templates/parameters.md) when they create their workspace.
 Envbuilder clones the repo and builds a container from the `devcontainer.json` specified in the repo.
 
+This is a legacy implementation.
+
 For the Docker-based Dev Containers integration, follow the [Configure a template for dev containers](../../extending-templates/devcontainers.md) documentation instead.
 
 You can create template files through the Coder dashboard, CLI, or you can choose a template from the
diff --git a/docs/admin/templates/managing-templates/devcontainers/devcontainer-releases-known-issues.md b/docs/admin/templates/managing-templates/devcontainers/devcontainer-releases-known-issues.md
@@ -1,5 +1,9 @@
 # Envbuilder Dev Container Releases and Known Issues
 
+Envbuilder is a legacy implementation of dev containers.
+
+For the Docker-based Dev Containers integration, follow the [Configure a template for dev containers](../../extending-templates/devcontainers.md) documentation instead.
+
 ## Release Channels
 
 Envbuilder provides two release channels:
diff --git a/docs/admin/templates/managing-templates/devcontainers/index.md b/docs/admin/templates/managing-templates/devcontainers/index.md
@@ -14,9 +14,9 @@ pre-approved by platform teams in registries like
 workflows, reduces the need for tickets and approvals, and promotes greater
 independence for developers.
 
-This doc explains how to use Envbuilder to integrate dev containers in a template.
+Envbuilder is a legacy implementation of dev containers.
 
-For the Docker-based Dev Containers integration, follow the [Configure a template for dev containers](../../extending-templates/devcontainers.md) documentation.
+For the Docker-based Dev Containers integration, follow the [Configure a template for dev containers](../../extending-templates/devcontainers.md) documentation instead.
 
 ## Prerequisites
 
diff --git a/docs/user-guides/devcontainers/index.md b/docs/user-guides/devcontainers/index.md
@@ -43,20 +43,6 @@ When a workspace with the dev containers integration starts:
 - Full SSH access directly into dev containers (`coder ssh <agent>.<workspace>.me.coder`).
 - Automatic port forwarding.
 
-## Comparison with Envbuilder-based Dev Containers
-
-| Feature        | Dev Containers                         | Envbuilder Dev Containers                    |
-|----------------|----------------------------------------|----------------------------------------------|
-| Implementation | Direct `@devcontainers/cli` and Docker | Coder's Envbuilder                           |
-| Target users   | Individual developers                  | Platform teams and administrators            |
-| Configuration  | Standard `devcontainer.json`           | Terraform templates with Envbuilder          |
-| Management     | User-controlled                        | Admin-controlled                             |
-| Requirements   | Docker access in workspace             | Compatible with more restricted environments |
-
-Choose the appropriate solution based on your team's needs and infrastructure constraints.
-
-Visit [Choose an approach to Dev Containers](../../admin/templates/extending-templates/dev-containers-envbuilder.md) for a more in-depth comparison.
-
 ## Known Limitations
 
 Currently, dev containers are not compatible with [prebuilt workspaces](../../admin/templates/extending-templates/prebuilt-workspaces.md).
