Skip to content

Commit ea9f003

Browse files
authored
docs: clarify dev containers entry point and reduce callouts (#21188)
The user guide jumped straight into integration details without explaining what dev containers are. Now it opens with a brief orientation linking to the spec, then explains this guide covers the Docker-based approach. Converted several NOTE callouts to prose where they were just cross-references or stacked unnecessarily. The Envbuilder index note was reframed to lead with its strengths rather than "we recommend the other thing." Also updates platform support to Linux only per current status. Refs #21157
1 parent f3e26ca commit ea9f003

File tree

4 files changed

+28
-40
lines changed

4 files changed

+28
-40
lines changed

docs/admin/integrations/devcontainers/envbuilder/index.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,12 @@ Unlike the [Dev Containers integration](../integration.md),
66
Envbuilder transforms the workspace image itself rather than running containers
77
inside the workspace.
88

9-
> [!NOTE]
10-
>
11-
> For most use cases, we recommend the
12-
> [Dev Containers integration](../integration.md),
13-
> which uses the standard `@devcontainers/cli` and Docker. Envbuilder is an
14-
> alternative for environments where Docker is not available or for
15-
> administrator-controlled dev container workflows.
9+
Envbuilder is well-suited for Kubernetes-native deployments without privileged
10+
containers, environments where Docker is unavailable or restricted, and
11+
workflows where administrators need infrastructure-level control over image
12+
builds, caching, and security scanning. For workspaces with Docker available,
13+
the [Dev Containers Integration](../integration.md) offers container management
14+
with dashboard visibility and multi-container support.
1615

1716
Dev containers provide developers with increased autonomy and control over their
1817
Coder cloud development environments.

docs/admin/integrations/devcontainers/integration.md

Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
11
# Configure a template for Dev Containers
22

3-
> [!NOTE]
4-
> For environments without Docker, see [Envbuilder](./envbuilder/index.md) as an alternative.
3+
This guide covers the Dev Containers Integration, which uses Docker. For
4+
environments without Docker, see [Envbuilder](./envbuilder/index.md) as an
5+
alternative.
56

67
To enable Dev Containers in workspaces, configure your template with the Dev Containers
78
modules and configurations outlined in this doc.
89

9-
> [!NOTE]
10-
>
11-
> Dev Containers require a **Linux or macOS workspace**. Windows is not supported.
10+
Dev Containers are currently not supported in Windows or macOS workspaces.
1211

1312
## Configuration Modes
1413

@@ -66,19 +65,10 @@ resource "coder_devcontainer" "my-repository" {
6665
}
6766
```
6867

69-
> [!NOTE]
70-
>
71-
> The `workspace_folder` attribute must specify the location of the dev
72-
> container's workspace and should point to a valid project folder containing a
73-
> `devcontainer.json` file.
74-
75-
<!-- nolint:MD028/no-blanks-blockquote -->
76-
77-
> [!TIP]
78-
>
79-
> Consider using the [`git-clone`](https://registry.coder.com/modules/git-clone)
80-
> module to ensure your repository is cloned into the workspace folder and ready
81-
> for automatic startup.
68+
The `workspace_folder` attribute must point to a valid project folder containing
69+
a `devcontainer.json` file. Consider using the
70+
[`git-clone`](https://registry.coder.com/modules/git-clone) module to ensure
71+
your repository is cloned and ready for automatic startup.
8272

8373
For multi-repo workspaces, define multiple `coder_devcontainer` resources, each
8474
pointing to a different repository. Each one runs as a separate sub-agent with

docs/manifest.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -321,7 +321,7 @@
321321
"icon_path": "./images/icons/circle-dot.svg"
322322
},
323323
{
324-
"title": "Dev Containers Integration",
324+
"title": "Dev Containers",
325325
"description": "Run containerized development environments in your Coder workspace using the dev containers specification.",
326326
"path": "./user-guides/devcontainers/index.md",
327327
"icon_path": "./images/icons/container.svg",

docs/user-guides/devcontainers/index.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,15 @@
1-
# Dev Containers Integration
1+
# Dev Containers
22

3-
The Dev Containers integration enables seamless creation and management of dev
4-
containers in Coder workspaces. This feature leverages the
5-
[`@devcontainers/cli`](https://github.com/devcontainers/cli) and
6-
[Docker](https://www.docker.com) to provide a streamlined development
7-
experience.
3+
[Dev containers](https://containers.dev/) define your development environment
4+
as code using a `devcontainer.json` file. Coder's Dev Containers integration
5+
uses the [`@devcontainers/cli`](https://github.com/devcontainers/cli) and
6+
[Docker](https://www.docker.com) to seamlessly build and run these containers,
7+
with management in your dashboard.
88

9-
> [!NOTE]
10-
> This guide covers the Dev Containers Integration, which uses Docker.
11-
> For environments without Docker, administrators can configure
12-
> [Envbuilder](../../admin/integrations/devcontainers/envbuilder/index.md)
13-
> as an alternative.
9+
This guide covers the Dev Containers integration. For workspaces without Docker,
10+
administrators can configure
11+
[Envbuilder](../../admin/integrations/devcontainers/envbuilder/index.md) instead,
12+
which builds the workspace image itself from your dev container configuration.
1413

1514
## Prerequisites
1615

@@ -20,7 +19,7 @@ experience.
2019

2120
Dev Containers integration is enabled by default. Your workspace needs Docker
2221
(via Docker-in-Docker or a mounted socket) and the devcontainers CLI. Most
23-
templates with Dev Containers support include both—see
22+
templates with Dev Containers support include both. See
2423
[Configure a template for dev containers](../../admin/integrations/devcontainers/integration.md)
2524
for setup details.
2625

@@ -115,8 +114,8 @@ in your `devcontainer.json`.
115114

116115
## Limitations
117116

118-
- **Linux and macOS only**Dev Containers are not supported on Windows
119-
workspaces
117+
- **Linux only**: Dev Containers are currently not supported in Windows or
118+
macOS workspaces
120119
- Changes to `devcontainer.json` require manual rebuild using the dashboard
121120
button
122121
- The `forwardPorts` property in `devcontainer.json` with `host:port` syntax

0 commit comments

Comments
 (0)