Hello Georg usually you put the box in a internal webserver, or publish in atlas, so instead of sharing a big file, you just put in a project a Vagranfile
easier to distribute this way. the vagrant file can be minimal, just to tell vagrant what box to use. If you have the box local, and you will name your box, say awesome.box you can do this vagrant init -m awesome then edit Vagrantifile and add config.vm.box_url = "awesome.box" that will do the trick other option is add the box manually, like vagrant box add --name awesome --provider=virtualbox then you can do vagrant init -m awesome vagrant up but there always must be a vagrantfile if you publish your boxes in atlas (with an url and externally hosted, or upload/hosted in atlas) you can use this: the box will be named user/awesome then will be easier vagrant init -m user/awesome vagrant up On Thu, Jun 18, 2015 at 8:03 PM, Georg Heiler <[email protected]> wrote: > Hi > > if I build a packer Image using a local builder like virtualbox or > parallels-iso do I still need a Vagrant-file in order to run my new box? > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
