Skip to content
Coder Docs

Add an Envbuilder template

Add an Envbuilder-compatible template so users can build dev containers from a repository.

On this page

Warning

Envbuilder is in maintenance mode with no new features planned.

The recommended way to use dev containers in Coder is the built-in Dev Containers Integration. To find the best approach for your deployment, ask in the Coder Discord server.

A Coder administrator adds an Envbuilder-compatible template to Coder. This allows the template to prompt the developer for their dev container repository's URL as a parameter when they create their workspace. Envbuilder clones the repo and builds a container from the devcontainer.json specified in the repo.

You can create template files through the Coder dashboard, CLI, or you can choose a template from the Coder registry:

  1. In the Coder dashboard, select Templates > New Template. The template builder opens.

  2. Select Upload an existing template at the bottom of the page to upload your Terraform files directly.

    The template builder does not currently include dev-container-compatible base templates.

  3. Upload your .zip or .tar.gz file, enter the details, then select Create template.

  4. Edit the template files to fit your deployment.

To set variables such as the namespace, go to the template in your Coder dashboard and select Settings from the ⋮ (vertical ellipsis) menu:

Choose Settings from the template's menu

Envbuilder Terraform provider

When using the Envbuilder Terraform provider, a previously built and cached image can be reused directly, allowing dev containers to start instantaneously.

Developers can edit the devcontainer.json in their workspace to customize their development environments:

# …
{
  "features": {
      "ghcr.io/devcontainers/features/common-utils:2": {}
  }
}
# …

Example templates

TemplateDescription
Docker dev containersDocker provisions a development container.
Kubernetes dev containersProvisions a development container on the Kubernetes cluster.
Google Compute Engine dev containerRuns a development container inside a single GCP instance. It also mounts the Docker socket from the VM inside the container to enable Docker inside the workspace.
AWS EC2 dev containerRuns a development container inside a single EC2 instance. It also mounts the Docker socket from the VM inside the container to enable Docker inside the workspace.

Your template can prompt the user for a repo URL with parameters:

Dev container parameter screen

Dev container lifecycle scripts

The onCreateCommand, updateContentCommand, postCreateCommand, and postStartCommand lifecycle scripts are run each time the container is started. This could be used, for example, to fetch or update project dependencies before a user begins using the workspace.

Lifecycle scripts are managed by project developers.

Next steps