Closed ezlee closed 7 years ago
Thats a very old packer.
Any change you can update?
I tried to use packer 1.0.0, but same issue. It worked with 0.8.6 2 weeks ago, I have to reinstall jenkins on the same server, and didn't change packer install, and now, it has this issue for packer ansible provisioner.
Your install is broken. Remove your current install directory and reinstall from packer.io/downloads. Be sure to read the note about upgrading from < 0.9.0.
how could it be broken? It is just one "packer" binary file to be copied to /usr/local/bin and all the other plugin binaries. I only have a packer-provisioner-ansible-local plugin and do not have the packer-provisioner-ansible plugin, but it worked for both provisioners before. I reinstalled Jenkins only, didn't make any changes for packer.
Packer now ships as a single binary. When upgrading from Packer < 0.9.0, you will need to remove the old
packer-*
plugins from your installation path.
There should be no more plugin binaries.
yes, didn't notice that. thanks a lot!
Is post-processor-docker-dockerfile still available? i get error: Failed to initialize build 'docker': post-processor type not found: docker-dockerfile
packer version 0.8.6, jenkins 2.42, ansible 2.1.1.0 on Jenkins server I was able to use packer to build gcp image without any issue before. But when I rebuild my jenkins box and re-configure packer to build the same gcp image, the packer "ansible" provider could not be discovered. I have both "ansible-local" and "ansible" remote provisioners plugins and build configuration defined in the config.json file. But only "ansible" provisioner was not able to be discovered.
debug info showing: Failed to initialize build 'gcp_image': provisioner type not found: ansible
What could be wrong with the ansible provisioner? I only have the /usr/local/bin//usr/local/bin/packer-provisioner-ansible-local plugin binary, do not have /usr/local/bin/packer-provisioner-ansible, but it was working before.