Nope. It keeps saying:
Bringing machine 'default' up with 'virtualbox' provider... ==> default: VirtualBox VM is already running.
I had to do a "vagrant destroy" of my previously running VM, then a "vagrant up" of both.
ruby --version ruby 2.0.0p353 (2013-11-22) [x64-mingw32] vagrant --version Vagrant 1.6.3
There you have a workaround.... however I am quite skeptical that Vagrant "fails" on such a basic operation... I am NOT impressed... I am unconditionally unimpressed by whatever turns around Ruby, the language is way too unstable and buggish when you compare to Java... I really wish all this Puppet/Vagrant world had not used Ruby as implementation language...
No comments:
Post a Comment