You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>If you run <code>dstack apply</code> and see <code>No fleets</code> status it can mean two things:</p>
4258
+
<divclass="tabbed-set tabbed-alternate" data-tabs="1:2"><inputchecked="checked" id="the-project-has-no-fleets" name="__tabbed_1" type="radio" /><inputid="no-matching-fleet-found" name="__tabbed_1" type="radio" /><divclass="tabbed-labels"><labelfor="the-project-has-no-fleets">The project has no fleets</label><labelfor="no-matching-fleet-found">No matching fleet found</label></div>
4259
+
<divclass="tabbed-content">
4260
+
<divclass="tabbed-block">
4261
+
<p>In this case, ensure you've created one before submitting runs. This can be either a <ahref="../../concepts/fleets/#backend-fleets">backend fleet</a> (if you are using cloud or Kubernetes) or an <ahref="../../concepts/fleets/#ssh-fleets">SSH fleet</a> (if you're using on-prem clusters).</p>
4262
+
<divclass="admonition info">
4263
+
<pclass="admonition-title">Backend fleets</p>
4264
+
<p>Note that creating <ahref="../../concepts/fleets/#backend-fleets">backend fleet</a> doesn't necessarily require provisioning instances upfront. If you set <code>nodes</code> to a range, <code>dstack</code> will be able to provision instances as required. See <ahref="../../concepts/fleets/#backend-fleets">backend fleet</a> for examples.</p>
4265
+
</div>
4266
+
</div>
4267
+
<divclass="tabbed-block">
4268
+
<p>This means fleets exist but run requirements do not match the configuration of the fleet. Review your fleets, and ensure that both run and fleet configuration are correct.</p>
<p>If you run <code>dstack apply</code> and don't see any instance offers, it means that
4232
4274
<code>dstack</code> could not find instances that match the requirements in your configuration.
4233
4275
Below are some of the reasons why this might happen.</p>
4234
4276
<blockquote>
4235
4277
<p>Feel free to use <code>dstack offer</code> to view available offers.</p>
4236
4278
</blockquote>
4237
-
<h4id="cause-1-no-fleets">Cause 1: No fleets<aclass="headerlink" href="#cause-1-no-fleets" title="Permanent link">¶</a></h4>
4238
-
<p>Make sure you've created a <ahref="../../concepts/fleets/">fleet</a> before submitting any runs.</p>
4239
-
<h4id="cause-2-no-backends">Cause 2: No backends<aclass="headerlink" href="#cause-2-no-backends" title="Permanent link">¶</a></h4>
4279
+
<h4id="cause-1-no-backends">Cause 1: No backends<aclass="headerlink" href="#cause-1-no-backends" title="Permanent link">¶</a></h4>
4240
4280
<p>If you are not using <ahref="../../concepts/fleets/#ssh-fleets">SSH fleets</a>, make sure you have configured at least one <ahref="../../concepts/backends/">backends</a>.</p>
4241
4281
<p>If you have configured a backend but still cannot use it, check the output of <code>dstack server</code> for backend configuration errors.</p>
4242
4282
<blockquote>
4243
4283
<p>You can find a list of successfully configured backends on the <ahref="../../concepts/projects/#backends">project settings page</a> in the UI.</p>
Make sure your configuration doesn't set any conflicting requirements, such as
4257
4297
<code>regions</code> that don't exist in the specified <code>backends</code>, or <code>instance_types</code> that
4258
4298
don't match the specified <code>resources</code>.</p>
4259
-
<h4id="cause-4-too-specific-resources">Cause 4: Too specific resources<aclass="headerlink" href="#cause-4-too-specific-resources" title="Permanent link">¶</a></h4>
4299
+
<h4id="cause-3-too-specific-resources">Cause 3: Too specific resources<aclass="headerlink" href="#cause-3-too-specific-resources" title="Permanent link">¶</a></h4>
4260
4300
<p>If you set a resource requirement to an exact value, <code>dstack</code> will only select instances
4261
4301
that have exactly that amount of resources. For example, <code>cpu: 5</code> and <code>memory: 10GB</code> will only
4262
4302
match instances that have exactly 5 CPUs and exactly 10GB of memory.</p>
4263
4303
<p>Typically, you will want to set resource ranges to match more instances.
4264
4304
For example, <code>cpu: 4..8</code> and <code>memory: 10GB..</code> will match instances with 4 to 8 CPUs
Copy file name to clipboardExpand all lines: docs/guides/troubleshooting/index.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,20 @@ and [this](https://github.com/dstackai/dstack/issues/1551).
28
28
29
29
## Typical issues
30
30
31
+
### No fleets { #no-fleets }
32
+
[//]: #(NOTE: This section is referenced in the CLI. Do not change its URL.)
33
+
34
+
If you run `dstack apply` and see `No fleets` status it can mean two things:
35
+
36
+
=== "The project has no fleets"
37
+
In this case, ensure you've created one before submitting runs. This can be either a [backend fleet](../concepts/fleets.md#backend-fleets) (if you are using cloud or Kubernetes) or an [SSH fleet](../concepts/fleets.md#ssh-fleets) (if you're using on-prem clusters).
38
+
39
+
!!! info "Backend fleets"
40
+
Note that creating [backend fleet](../concepts/fleets.md#backend-fleets) doesn't necessarily require provisioning instances upfront. If you set `nodes` to a range, `dstack` will be able to provision instances as required. See [backend fleet](../concepts/fleets.md#backend-fleets) for examples.
41
+
42
+
=== "No matching fleet found"
43
+
This means fleets exist but run requirements do not match the configuration of the fleet. Review your fleets, and ensure that both run and fleet configuration are correct.
44
+
31
45
### No offers { #no-offers }
32
46
[//]: #(NOTE: This section is referenced in the CLI. Do not change its URL.)
33
47
@@ -37,19 +51,15 @@ Below are some of the reasons why this might happen.
37
51
38
52
> Feel free to use `dstack offer` to view available offers.
39
53
40
-
#### Cause 1: No fleets
41
-
42
-
Make sure you've created a [fleet](../concepts/fleets.md) before submitting any runs.
43
-
44
-
#### Cause 2: No backends
54
+
#### Cause 1: No backends
45
55
46
56
If you are not using [SSH fleets](../concepts/fleets.md#ssh-fleets), make sure you have configured at least one [backends](../concepts/backends.md).
47
57
48
58
If you have configured a backend but still cannot use it, check the output of `dstack server` for backend configuration errors.
49
59
50
60
> You can find a list of successfully configured backends on the [project settings page](../concepts/projects.md#backends) in the UI.
51
61
52
-
#### Cause 3: Requirements mismatch
62
+
#### Cause 2: Requirements mismatch
53
63
54
64
When you apply a configuration, `dstack` tries to find instances that match the
0 commit comments