Incompatible with vagrant post-processor since 2.0

[stephenreay]

Code of Conduct

• I have read and agree to the Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Packer Version

1.15.3

Packer Plugin Version

2.1.2

Plugin Component

• vmware-iso
• vmware-vmx

Hypervisor

• VMware Fusion (macOS)
• VMware Workstation (Windows/Linux)
• VMware ESX (Baremetal)

Hypervisor Version

26H1

Hypervisor Operating System

macOS 15.7.7

Description

A packer config that works with the VMware plugin correctly produces a vagrant .box when using VMware plugin version 1.2.0

From 2.0 (after updating to set the tools_mode option) the VM still builds correctly, but fails at the final step with the following error:

* Post-processor failed: Unknown artifact type, can't build box: vmware.desktop

Packer Configuration

https://github.com/Koalephant/packer-plugin-vmware/tree/error-status-2x/example/iso

I've modified the "example" configuration to show the issue, with two changes:

• fixed the current Debian ISO version link
• added vagrant post processor to the build config

Debug Output

https://gist.github.com/stephenreay/8d17670c22b955ec91d6e70bfd612ac7

Panic Output

No response

Expected Behavior

The post-processor should create a vagrant .box file from the input artifact (the VM)

Actual Behavior

The post-processor throws an error "Unknown artifact type, can't build box: vmware.desktop"

Steps to Reproduce

git clone https://github.com/Koalephant/packer-plugin-vmware
cd packer-plugin-vmware
git checkout error-status-2x
packer init -force .
packer build -var-file=pkrvars/debian/fusion-arm64.pkrvars.hcl .

Environment Details

Reproduced on a M2 Ultra Mac Studio and an Intel Core i7 Mac mini

Screenshots

No response

References

No response

[stephenreay]

Note: I had to "lie" and say I've read the code of conduct. I guess I did read what it links to, but it just says "404 page not found" rather than any kind of actual Code of Conduct.

[tenthirtyam]

I've submitted pull request #151 to hashicorp/packer-pluign-vagrant that updates the associated builder ID used in this plugin as of v2.0.0+. I've reached out directly to the maintainers at HashiCorp for a review request.

Ryan

[tenthirtyam]

Note: I had to "lie" and say I've read the code of conduct. I guess I did read what it links to, but it just says "404 page not found" rather than any kind of actual Code of Conduct.

Thanks for letting me know. I've addressed this in the issue templates.

Ryan