search

hashicorp / packer

Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
http://www.packer.io
Other
15.05k stars 3.32k forks source link

error initializing provisioner 'windows-update': Unknown provisioner #11777

Closed audioeptesicus closed 2 years ago

audioeptesicus commented 2 years ago

Running packer 1.8.0 from a Windows 2019 server.

I'm running packer from C:\Scripts\Packer and have the environment variable set. I have placed the packer-plugin-windows-update_v0.14.0_x5.0_windows_amd64.exe plugin in multiple directories (where packer.exe resides, where the .json/.pkr.hcl files are saved, in various plugin directories I have created based on recommended paths) and cannot avoid the error.

The packer log finds the plugins, but does note the following:

2022/05/13 08:31:52 ui error: Error: Unknown provisioner type "windows-update"

  on Windows_Builds\Win2022_Base\Win2022_Base.pkr.hcl line 129:
  (source code not available)

What am I doing wrong here?

tenthirtyam commented 2 years ago

windows-update is a community provisioner. I would suggest opening an issue at rgl/packer-plugin-windows-update.

Ryan Johnson Staff II Solutions Architect | VMware, Inc.

animatco commented 2 years ago

As you can see in that repo you need to add to either a init.pkr.hcl file or within your pkr.hcl

packer { required_plugins { windows-update = { version = "0.14.1" source = "github.com/rgl/windows-update" } } }

Then run packer init whatever.pkr.hcl

nywilken commented 2 years ago

@tenthirtyam and @animatco thanks for the assist on this issue. I'm going to close as the question has been answered.

@audioeptesicus external Packer plugins need to be installed by running packer init or manually using the manual installation process outlined in the documentation https://www.packer.io/plugins#installing-plugins

github-actions[bot] commented 2 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.