Replies: 5 comments 5 replies
-
Hi, were you able to get a solution? I have been trying to install WSL using winget through packer but packer doesnt even recognize winget install. what did you do to get winget install to work through packer? |
Beta Was this translation helpful? Give feedback.
-
I have been able to install both the current and pre-release versions of winget through packer without any issues but am still unable to actually install any packages with the same issue described above. Hope the following may help you in your pursuit though: Current Version: Pre-release version: I don't believe the elevated user is needed but I have tried both ways and it works. I included an example for each just in case. Build.WinRMPassword is a native packer variable for the auto-generated password local admin(packer) account. |
Beta Was this translation helpful? Give feedback.
-
That is the exact error and experience I have.
…________________________________
From: user22100 ***@***.***>
Sent: Thursday, June 15, 2023 7:41:35 PM
To: microsoft/winget-cli ***@***.***>
Cc: John Hoffman ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/winget-cli] I am having trouble using winget with packer. (Discussion #3326)
When i run commands like these:
Write-Host "Installing Rancher"
winget install rancher-desktop --silent --accept-source-agreements --accept-package-agreements
I keep getting this error:
Installing Rancher
azure-arm: The msstore source requires that you view the following agreements before using.
azure-arm: Terms of Transaction: https://aka.ms/microsoft-store-terms-of-transaction
azure-arm: The source requires the current machine's 2-letter geographic region to be sent to the backend service to function properly (ex. "US").
azure-arm:
azure-arm: Failed when searching source: winget
azure-arm: An unexpected error occurred while executing the command:
azure-arm: 0x8a15000f : Data required by the source is missing
azure-arm:
azure-arm: No packages were found among the working sources.
==> azure-arm: Provisioning step had errors: Running the cleanup provisioner, if present...
Are you running into anything like that?
—
Reply to this email directly, view it on GitHub<#3326 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKQZN66QMPU4TOH74I7FVJDXLOMS7ANCNFSM6AAAAAAZBA3PAU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Seems to be a known issue: |
Beta Was this translation helpful? Give feedback.
-
Is there anyone who has had success installing winget applications in a packer build on windows 11 23h2? |
Beta Was this translation helpful? Give feedback.
-
I am trying to install the Adobe Reader package using a PowerShell provisioner within my packer config. In short, when I execute the winget install command from within the PowerShell provisioner, it always fails with the "0x8a15000f: Data required by the source is missing" message. I can pause the packer build, RDP into the build VM, execute the exact same command from a PowerShell prompt, and it works without issue. I have tried the latest winget version and a couple pre-release versions. I believe it is something related to PS remoting but just have not been able to find anything while scouring the web for answers. Maybe something that logging into the machine interactively fixes. Any help would be greatly appreciated.
winget install --id Adobe.Acrobat.Reader.32-bit --accept-package-agreements --accept-source-agreements
Beta Was this translation helpful? Give feedback.
All reactions