First to ask the obvious question: Are you doing vagrant up in the directory where the Vagrantfile is? Because all vagrant init is doing is create Vagrantfile with a stock content (well and the name you have provided)
Have you edited the Vagrantfile resulting from vagrant init? Cheers, V.-. On Thu, Jan 8, 2015 at 10:34 AM, Jovan Jokic <[email protected]> wrote: > Following is occurring: > > > vagrant init hashicorp/precise32 > > A `Vagrantfile` has been placed in this directory. You are now > > ready to `vagrant up` your first virtual environment! Please read > > the comments in the Vagrantfile as well as documentation on > > `vagrantup.com` for more information on using Vagrant. > > > > vagrant up > > A Vagrant environment or target machine is required to run this > > command. Run `vagrant init` to create a new Vagrant environment. Or, > > get an ID of a target machine from `vagrant global-status` to run > > this command on. A final option is to change to a directory with a > > Vagrantfile and to try again. > > And i am spinning in circles. > Vagrant 1.6.5 > VBox 4.3.20 > > -- > 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. > -- http://www.ampelofilosofies.gr -- 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.
