You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Overview of the Issue
I'm using Mac M1 and rely on VMWare Fusion (In Packer I'm using VMWare ISO builder) and vagrant as a post-processor.
Locally when using the generated box, everything works fine, however when I push the box to hashicorp cloud then use that box instead, it throws the following error:
Provider expected: vmware_fusion Provider of box: vmware_desktop (Somehow Packer just throws vmware_desktop all the time instead of vmware_fusion).
I'm unable to find a way to change this, what I tried was in the post-processor to do the following
And while it modifies the file, still the file that gets placed in the generated vagrant box contains vmware_destkop instead.
What i do as a workaround is very manual, that is to extract the box, modify the file, tar compress the box again then push it but .. isn't there a way to avoid all that ? A way to specify that in the generated metadata.json file I need to use vmware_fusion as the provider ?
Reproduction Steps
Steps to reproduce this issue
On Mac M1 if you use Packer with VMWare Fusion you should be able to reproduce by
Generate a Vagrant box
Push it to Hashicorp cloud
Use that box, it should throw the aforementioned issue.
Community Note
Overview of the Issue
I'm using Mac M1 and rely on VMWare Fusion (In Packer I'm using VMWare ISO builder) and vagrant as a post-processor.
Locally when using the generated box, everything works fine, however when I push the box to hashicorp cloud then use that box instead, it throws the following error:
Provider expected: vmware_fusion Provider of box: vmware_desktop
(Somehow Packer just throws vmware_desktop all the time instead of vmware_fusion).I'm unable to find a way to change this, what I tried was in the post-processor to do the following
And while it modifies the file, still the file that gets placed in the generated vagrant box contains vmware_destkop instead.
What i do as a workaround is very manual, that is to extract the box, modify the file, tar compress the box again then push it but .. isn't there a way to avoid all that ? A way to specify that in the generated metadata.json file I need to use vmware_fusion as the provider ?
Reproduction Steps
Steps to reproduce this issue
On Mac M1 if you use Packer with VMWare Fusion you should be able to reproduce by
Packer version v1.11.2
Simplified Packer Template
Operating system and Environment details
Apple M1 Pro
MacOS Sequoia 15.3.1
VMWare Fusion 13.6.2
Packer 1.11.2
Vagrant 2.4.3
The text was updated successfully, but these errors were encountered: