Skip to content

Commit 4658b66

Browse files
authored
Merge pull request #78733 from zr-msft/ds-cloud-shell-update
[Dev Spaces] updated troubleshooting step to make it clearer that you…
2 parents d307161 + b343ec6 commit 4658b66

File tree

2 files changed

+14
-9
lines changed

2 files changed

+14
-9
lines changed

articles/dev-spaces/how-to/create-cluster-cloud-shell.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers,
1212
---
1313
# Create a Kubernetes cluster using Azure Cloud Shell
1414

15-
You can use [Azure Cloud Shell](/azure/cloud-shell) to create a cluster for Azure Dev Spaces by using the **Try It** button from this page. If you aren't signed in, follow the prompts to sign in with an Azure account, then type the commands at the Azure Cloud Shell prompt when it appears.
15+
You can use [Azure Cloud Shell](/azure/cloud-shell) to create an Azure Kubernetes Service cluster by using the **Try It** button from this page. If you aren't signed in, follow the prompts to sign in with an Azure account, then type the commands at the Azure Cloud Shell prompt when it appears.
1616

1717
## Create the cluster
1818

@@ -34,5 +34,8 @@ It takes a few minutes to create the cluster. When complete, the output is show
3434

3535
See [Azure Dev Spaces](/azure/dev-spaces/) for links to full tutorials.
3636

37+
> [!IMPORTANT]
38+
> Many of the Azure Dev Spaces quickstarts and tutorials use the Azure Dev Spaces CLI to perform operations. You cannot install the Azure Dev Spaces CLI in the Azure Cloud Shell.
39+
3740

3841
[supported-regions]: ../about.md#supported-regions-and-configurations

articles/dev-spaces/troubleshooting.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -30,24 +30,26 @@ Currently, Azure Dev Spaces works best when debugging a single instance, or pod.
3030

3131
## Error 'Failed to create Azure Dev Spaces controller'
3232

33+
### Reason
3334
You might see this error when something goes wrong with the creation of the controller. If it's a transient error, delete and recreate the controller to fix it.
3435

35-
### Try:
36+
### Try
3637

37-
To delete the controller, use the Azure Dev Spaces CLI. It’s not possible to do it in Visual Studio or Cloud Shell. To install the AZDS CLI, first install the Azure CLI, and then run this command:
38+
Delete the controller:
3839

39-
```cmd
40-
az aks use-dev-spaces -g <resource group name> -n <cluster name>
40+
```bash
41+
azds remove -g <resource group name> -n <cluster name>
4142
```
4243

43-
And then run this command to delete the controller:
44+
You must use the the Azure Dev Spaces CLI to delete a controller. It’s not possible to delete a controller from Visual Studio. You also cannot install the Azure Dev Spaces CLI in the Azure Cloud Shell so you cannot delete a controller from the Azure Cloud Shell.
45+
46+
If you do not have the Azure Dev Spaces CLI installed, you can first install it using the following command then delete your controller:
4447

4548
```cmd
46-
azds remove -g <resource group name> -n <cluster name>
49+
az aks use-dev-spaces -g <resource group name> -n <cluster name>
4750
```
4851

49-
Recreating the controller can be done from the CLI or Visual Studio. Follow the instructions in the tutorials as if starting for the first time.
50-
52+
Recreating the controller can be done from the CLI or Visual Studio. See the [Team development](quickstart-team-development.md) or [Develop with .NET Core](quickstart-netcore-visualstudio.md) quickstarts for examples.
5153

5254
## Error 'Service cannot be started.'
5355

0 commit comments

Comments
 (0)