Azure-docs: Can't find 'azds'

[timjroberts-inty]

When generating the Helm and Docker assets, the docs call for you to run azds prep --public. However, the azds command doesn't appear to be on my path, and I'm not sure what has installed it. I have installed version 2.0.38 of the azure-cli but can't get beyond this point in the docs.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 50c97296-51bc-14be-1888-8b3d9967a1b7
• Version Independent ID: 8c1d6961-9da2-4ce5-5cb1-b81f5287a278
• Content: Create a Kubernetes dev space in the cloud - Azure Dev Spaces
• Content Source: articles/dev-spaces/quickstart-netcore.md
• Service: azure-dev-spaces
• GitHub Login: @ghogen
• Microsoft Alias: ghogen

[MohitGargMSFT]

@timjroberts-inty Thanks for your feedback! We will investigate and update as appropriate.

[timjroberts-inty]

I can confirm that I have the dev-spaces-preview extension loaded:

> az extension list
[
  {
    "extensionType": "whl",
    "name": "dev-spaces-preview",
    "version": "0.1.6"
  }
]

[lisaguthrie]

azds.exe should be in C:\Program Files\Microsoft SDKs\Azure\Azure Dev Spaces CLI (Preview)

If it's not there, you need to run: az aks use-dev-spaces -n [AKS cluster name] -g [resource group name]

We've seen a lot of confusion from customers (including myself, at first :) who start in Visual Studio and then switch to the CLI. They think that they don't need to run the use-dev-spaces command because they've already set up the AZDS controller in VS. But if they don't run that command, they never get azds.exe.

This would be good to add to the troubleshooting docs.

[kobulloc-MSFT]

@ghogen In line with Lisa's response, let's get that added to the troubleshooting document.

[timjroberts-inty]

Thanks @lisaguthrie. I'm not using Visual Studio, but instead VSCode and CLI on a Mac. I don't remember seeing or issuing the az aks use-dev-spaces ... command though, so that is likely it. I've stood down my test cluster at the moment, but I'll give it all another go sometime next week.

[SunnyOswal]

I was getting same error on VSCODE and CLI on windows 10. There were no errors reported for az aks use-dev-spaces ....... command.
Workaround/Fix: Restart VsCode and azds prep --public runs fine.

[sebgod]

If you just installed the extension, you have to restart VS Code otherwise it can't find 'azds' in the path

[ghogen]

in-progress

[timjroberts-inty]

I can confirm that my issue of the missing 'azds' command was because I hadn't run the 'az aks use-dev-spaces -n [AKS cluster name] -g [resource group name]' command. I've run through the tutorial again, and all works!

[pjirsa]

i'm having the same issue. i run 'az aks use-dev-spaces -g mygroup -n mycluster' and it responds with '[K - Searching ..' then it returns to the prompt and azds is not found.

[tylerjwatson]

@pjirsa I am getting the same issue as well. Installed on Ubuntu 19.04

Edit: Same behaviour on Windows 10

[JerryWang20]

i also meet the issue for i run 'az aks use-dev-spaces -g mygroup -n mycluster' and it responds with '[K - Searching ..' what's the solution for it?

[diasbrito]

@JerryWang20 Did you get the solution? I'm going through the same mistake.

[JerryWang20]

You may need install the latest version for Azure CLI, Azure fixed it in latest version.

[pjirsa]

The reason this happened to me was that I was only a co-admin on my azure subscription and not assigned the owner role via RBAC.