Closed zkhcohen closed 3 years ago
Never tried it like that. You could try running in your machine and/or install it with packer init instead.
Never tried it like that. You could try running in your machine and/or install it with packer init instead.
Switching from the built-in Packer extension to the riezebosch version, and using Packer init resolved the issue!
Thanks.
What is the riezebosch version
?
What is the
riezebosch version
?
https://marketplace.visualstudio.com/items?itemName=riezebosch.Packer
Interesting. I never really used Azure DevOps. That seems to be equivalent to the packer github actions.
Is there any particular reason for using Azure DevOps over GitHub Actions?
To create the Virtual Machines are you using https://www.packer.io/docs/builders/azure/arm?
Is there any particular reason for using Azure DevOps over GitHub Actions?
We use Azure DevOps to integrate with our hybrid cloud environment, not GitHub. On-premise, I'm hosting this in Docker to integrate with VMWare clusters.
To create the Virtual Machines are you using https://www.packer.io/docs/builders/azure/arm?
ARM is utilized for the provisioning of the temporary VMs during the image build process, but the final VMs created out of the golden image are deployed using Terraform.
On-premise, I'm hosting this in Docker to integrate with VMWare clusters.
What do you mean by "hosting in docker"? Can you explain what is the relation between docker, golden image, and a VMware VM? And what is the flow between those? :-)
What do you mean by "hosting in docker"? Can you explain what is the relation between docker, golden image, and a VMware VM? And what is the flow between those? :-)
Packer is containerized in Docker. Running the Packer build generates a 'golden image' of Windows Server which is deployed to a VMware ESXi cluster.
Check out the builders here: https://www.packer.io/docs/builders/vmware
I see, I now understand what you mean by hosted in docker
. What is being hosted is packer
and you build it from there.
Hey.
I receive the following issue when attempting to use this Packer Provisioner with Packer 1.7.2 installed to a VSTS Azure Devops Pipeline via Chocolatey...
Initial spin-up of validation stage where it discovers the internal plugin:
The specific failure point:
It's worth noting that I'm simply copying the plugin .exe file to the path: C:\Users\VssAdministrator\AppData\Roaming\packer.d\plugins
Copying it next to the packer.exe (C:\ProgramData\Chocolatey\bin\packer.exe) results in a failure to detect the plugin, despite:
2021/07/02 00:25:57 [TRACE] discovering plugins in .
Any ideas what the issue could be?