the vagrant command you are having is coming from what looks like the very old gem
if you installed vagrant from a gem, you need to remove it first. whats the output of . vagrant version On Wed, Nov 1, 2017 at 11:35 PM, <[email protected]> wrote: > Hi, > > No luck. > > [docker@lab p64]$ vagrant init -m hashicorp/precise64 > Thanks for wanting to use Vagrant! Unfortunately, this is not the way > to install Vagrant anymore. We now make installers for the various > operating > systems Vagrant supports. > > Vagrant is no longer distributed as a RubyGem. Please download the latest > version for your operating system from the URL below. If you still wish > to use the RubyGem version, you can manually install version 1.0.7. Note > that > the RubyGem version hasn't been updated in over a year and will no longer > receive any updates. > > Prior to installing Vagrant using the installer, make sure you uninstall > all your Vagrant gems, since they sometimes conflict. > > http://www.vagrantup.com > > If you want to learn more about why we don't distribute using RubyGems > anymore, please read this: http://mitchellh.com/abandoning-rubygems > > > > > Regards, > Vikas > > On Thursday, 2 November 2017 03:32:16 UTC+5:30, [email protected] wrote: > >> i want to build it from cloned github repository for working with >> kubernetes >> >> os : centos 7 ,3.10.0-514.16.1.el7.x86_64 >> virtualbox : 5.1.28 >> vagrant : version 2 >> >> >> >> >> Thanks for wanting to use Vagrant! Unfortunately, this is not the way >> to install Vagrant anymore. We now make installers for the various >> operating >> systems Vagrant supports. >> >> Vagrant is no longer distributed as a RubyGem. Please download the latest >> version for your operating system from the URL below. If you still wish >> to use the RubyGem version, you can manually install version 1.0.7. Note >> that >> the RubyGem version hasn't been updated in over a year and will no longer >> receive any updates. >> >> Prior to installing Vagrant using the installer, make sure you uninstall >> all your Vagrant gems, since they sometimes conflict. >> >> http://www.vagrantup.com >> >> If you want to learn more about why we don't distribute using RubyGems >> anymore, please read this: http://mitchellh.com/abandoning-rubygems >> > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > 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]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/ec273353-523b-4515-a497-0bf3cf73e399%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/ec273353-523b-4515-a497-0bf3cf73e399%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezsw%3DdsB6u5ZRBYE-1Ot7ZpeU5BwrZ471XyvWZpOY1ymw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
