Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Using Vagrant to provision Powershell scripts onto a custom AMI using Packer #545

Open
degan93 opened this issue Jun 22, 2018 · 1 comment

Comments

@degan93
Copy link

degan93 commented Jun 22, 2018

Hello,

I have created a custom Windows AMI using Packer.
I am then trying to use Vagrant to provision more software (using Powershell scripts) onto the AMI.

Every time you run Vagrant, it always asks to specify a box file.
vm:

  • A box must be specified.

Because I used Packer to create an AMI, it doesn't give you an actual box file, it only provides a custom AMI ID.

Is there a way to configure the Vagrant file to specify an AMI ID instead of a box file?

@dragon788
Copy link

Did you follow the directions from the README to use the dummy box name and supply the other AWS information?
https://github.com/mitchellh/vagrant-aws#quick-start

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants