microsoft / microsoft/winget-cli
Doesn't work with Azure VM CustomScriptExtension
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
I have an Azure VM and want to run winget install commands or winget configuration (DSC) using VM Extension (Microsoft.Compute.CustomScriptExtension).
But it fails because the user used by the extension cannot run and cannot even find winget cli.
Steps to reproduce
- Create Azure VM
- Add vm extension of type Microsoft.Compute.CustomScriptExtension and give it winget commands.
- You should see an error saying that winget cli was not found.
Expected behavior
I expect the Azure VM extension to be able to run the winget commands.
Actual behavior
Error: winget command was not found.
Environment
any version of winget
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on an Azure VM with Microsoft.Compute.CustomScriptExtension, using the winget commands described in the issue. Investigate why the extension user cannot find or run the winget CLI; done means the extension can execute winget install or configuration commands successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100