vsphere packer build with -force flag doesn't completely remove existing files - intentional?

13 views
Skip to first unread message

easyspires

unread,
Apr 14, 2022, 2:03:23 PMApr 14
to Packer
Running 1.8.0 on Centos7.

Building a template on vsphere with -force flag results in the encouraging message:

 the vm/template Packer-Windows-Server-2019 already exists, but deleting it due to -force flag

but it actually leaving that folder in place with a single packer-tmp-created-floppy.flp file in it and creates the new template in a new _1 folder.

Interestingly, the new build folder does not contain that .flp file. 

Any ideas on what I am missing to get this to clean up after itself? 
Reply all
Reply to author
Forward
0 new messages