Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

docs: add dev containers and scheduling to prebuilt workspaces known issues#18816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
SasSwart merged 8 commits intomainfrom18806-prebuilds-known-limits
Aug 22, 2025
Merged
Changes from1 commit
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
PrevPrevious commit
remove defunct documentation for prebuilt workspaces
  • Loading branch information
@SasSwart
SasSwart committedAug 22, 2025
commitcde74d0c83a505ca5c6b1730a8beeadca082007a
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -4,6 +4,7 @@ Prebuilt workspaces (prebuilds) reduce workspace creation time with an automatic
ready-to-use workspaces for specific parameter presets.

The template administrator defines the prebuilt workspace's parameters and number of instances to keep provisioned.
The desired number of workspaces are then provisioned transparently.
When a developer creates a new workspace that matches the definition, Coder assigns them an existing prebuilt workspace.
This significantly reduces wait times, especially for templates with complex provisioning or lengthy startup procedures.

Expand DownExpand Up@@ -281,13 +282,6 @@ For example, the [`ami`](https://registry.terraform.io/providers/hashicorp/aws/l
has [`ForceNew`](https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/ec2/ec2_instance.go#L75-L81) set,
since the AMI cannot be changed in-place._

#### Updating claimed prebuilt workspace templates

Once a prebuilt workspace has been claimed, and if its template uses `ignore_changes`, users may run into an issue where the agent
does not reconnect after a template update. This shortcoming is described in [this issue](https://github.com/coder/coder/issues/17840)
and will be addressed before the next release (v2.23). In the interim, a simple workaround is to restart the workspace
when it is in this problematic state.

### Monitoring and observability

#### Available metrics
Expand All@@ -310,19 +304,3 @@ These logs provide information about:
1. Creation and deletion attempts for prebuilt workspaces.
1. Backoff events after failed builds.
1. Claiming operations.

## Known Issues and Limitations

Some known limitations of prebuilt workspaces include:

- **Organizations**

Prebuilt workspaces can only be used with the default organization.

[View issue](https://github.com/coder/internal/issues/364)

- **Dev containers**

Prebuilt workspaces do not work reliably with the [dev containers integration](../extending-templates/devcontainers.md).

If your project relies on a dev container configuration, you should disabling prebuilds or carefully test their behavior before enabling them.
Loading
[8]ページ先頭
©2009-2025 Movatter.jp