Consider template.json:

If i do packer build template.json I'll get:

It doesn't matter if i try to force it with:

I've tested with version 1.1.2 and 1.1.3 and both of them fail.

C:Program FilesOracleVirtualBoxVBoxGuestAdditions.iso is the default path after installing latest VirtualBox release.

Is there anything wrong with template.json or is this a bug? First time using go/packer so i'm probably missing some newbie stuff.

Thanks in advance!

@SwampDragons Hi there, any clue about this one? Please take a look to this test using the above template.

Asking to you cos I've seen this #5609 and it feels this is kinda related.

Thanks.

If this doesn't work on the 1.1.3-dev binary linked in that other ticket it isn't directly related to the issue I referenced when closing that ticket. Did this work on 1.1.1? Has this worked with any Packer version?

Well, I had tried using the virtualbox-provisioner with few versions of packer and none of them seemed to work with this basic feature, after seeing nobody was replying to the ticket i've just decided to discard the idea of using packer till becomes mature enough and just coming back to fabric to provisioning my boxes ;) .

Btw, is this project maintained by hashicorp employees or just external contributors?

There are two Hashicorp employees dedicated to Packer, but both of us are located in the United States and were on vacation for Thanksgiving last week. Sorry we didn't acknowledge your ticket earlier; hopefully you'll give it another chance sometime.

@SwampDragons Oh, thanks for the fast reply, good to hear that... My bad, I assumed very fast the project was unmaintained and i've thrown the towel too fast. But if it's so I'm willing to try again of course.

In any case, I'm a c++/python developer with 0% knowledge of rust so not sure whether I'll be able to contribute to help providing any PR. But still... if you need help to speed up or testing the tickets, please let me know and I'll help to test it out for sure.

To be honest, I deploy from windows to linux boxes quite a lot and few months ago was considering ansible and other alternatives... but they weren't great for this so I just got stuck with fabric. When I've heard about the existence of packer 5 days ago in the #vagrant channel I just thought 'Wow, this is it, this tool rocks too much and is the ideal one beating the other alternatives out there with poor windows support'.

Anyway, thanks for the fast reply.

Cool -- We do try to support windows properly but I will admit that we're not always quite as successful as we'd like. I'll have to spin up a windows 10 vm with virtualbox to test this out, but I'll get on it once I've finished triaging tickets that piled up during the holiday. Until then... my gut instinct is that this may be an issue with how we're handling the space in the filepath.

BTW if you've got a C++/Python background then golang (Packer's in go, not Rust) should be right up your alley. To me, it feels something like a nice mix of the two.

this is a dupe of #5559 I think.

could help us by testing the build in #5559 (comment)

I don’t think these are dupes, actually. Will investigate tomorrow though.

@brupelo I think you were right; this looks like it was a dupe of #5609 -- I just got a windows 10 box running virtualbox with a dev build of packer, and I didn't run into your error... which means I believe this should be fixed for you in the next release.

Meanwhile, the binary I uploaded here: #5589 (comment) should tide you over if you want to try on a dev-build.