@@ -82,4 +82,54 @@ Please contact your Coder sales contact, or visit https://coder.com/contact/sale
82
82
Prebuilds only become eligible to be claimed by users once the workspace's agent is a) running and b) all of its startup
83
83
scripts have completed.
84
84
85
- If a prebuilt workspace is not eligible, view its agent logs to diagnose the problem.
85
+ If a prebuilt workspace is not eligible, view its agent logs to diagnose the problem.
86
+
87
+ ## CoderdUnprovisionedPrebuiltWorkspaces
88
+
89
+ The number of running prebuilt workspaces is lower than the desired instances. This could be for several reasons,
90
+ ordered by likehood:
91
+
92
+ ### Experiment/License
93
+
94
+ The prebuilds feature is currently gated behind an experiment * and* a premium license.
95
+
96
+ Ensure that the prebuilds experiment is enabled with ` CODER_EXPERIMENTS=workspace-prebuilds ` , and that you have a premium
97
+ license added.
98
+
99
+ ### Preset Validation Issue
100
+
101
+ Templates which have prebuilds configured will require a configured preset defined, with ALL of the required parameters
102
+ set in the preset. If any of these are missing, or any of the parameters - as defined - fail validation, then the prebuilds
103
+ subsystem will refuse to attempt a workspace build.
104
+
105
+ Consult the coderd logs for more information; look out for errors or warnings from the prebuilds subsystem.
106
+
107
+ ### Template Misconfiguration or Error
108
+
109
+ Prebuilt workspaces cannot be provisioned due to some issue at ` terraform apply ` -time. This could be due to misconfigured
110
+ cloud resources, improper authorization, or any number of other issues.
111
+
112
+ Visit the Workspaces page, change the search term to ` owner:prebuilds ` , and view on the previously failed builds. The
113
+ error will likely be quite obvious.
114
+
115
+ ### Provisioner Latency
116
+
117
+ If your provisioners are overloaded and cannot process provisioner jobs quickly enough, prebuilt workspaces may be affected.
118
+ There is no prioritization at present for prebuilt workspace jobs.
119
+
120
+ Ensure your provisioners are appropriately resources (i.e. you have enough instances) to handle the concurrent build demand.
121
+
122
+ ### Use of Workspace Tags
123
+
124
+ If you are using ` coder_workspace_tags ` ([ docs] ( https://coder.com/docs/admin/templates/extending-templates/workspace-tags ) )
125
+ in your template, chances are you do not have any provisioners running or they are under-resourced (see ** Provisioner Latency** ).
126
+
127
+ Ensure your running provisioners are configured with your desired tags.
128
+
129
+ ### Reconciliation Loop Issue
130
+
131
+ The prebuilds subsystem runs a _ reconciliation loop_ which monitors the state of prebuilt workspaces to ensure the desired
132
+ number of instances are present at all times. Workspace Prebuilds is currently a BETA feature and so there could be a bug
133
+ in this _ reconciliation loop_ , which should be reported to Coder.
134
+
135
+ Examine your coderd logs for any errors or warnings relating to prebuilds.
0 commit comments