vagrant up command not working in vagrant 2 version ,getting following message .please provide work around

88 views
Skip to first unread message

vikas...@gmail.com

unread,
Nov 1, 2017, 6:02:16 PM11/1/17
to Vagrant
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.


If you want to learn more about why we don't distribute using RubyGems
anymore, please read this: http://mitchellh.com/abandoning-rubygems

vikas...@gmail.com

unread,
Nov 1, 2017, 6:05:32 PM11/1/17
to Vagrant
github repository 


Regards,
Vikas

Alvaro Miranda Aguilera

unread,
Nov 1, 2017, 6:09:10 PM11/1/17
to vagra...@googlegroups.com
hello

you need to download the installer from http://www.vagrantup.com

current version 2.x

install virtualbox 5.1.30

test it works

mkdir p64
cd p64
vagrant init -m hashicorp/precise64
vagrant up

if works, then you can test other boxes/repos.

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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/57db8777-0d83-4c69-be62-6af9712ddc45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

vikas...@gmail.com

unread,
Nov 1, 2017, 6:35:11 PM11/1/17
to Vagrant
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.


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, vikas...@gmail.com wrote:

Alvaro Miranda Aguilera

unread,
Nov 1, 2017, 7:12:35 PM11/1/17
to vagra...@googlegroups.com
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


--
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 vagrant-up+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Vikas Ga

unread,
Nov 1, 2017, 7:17:36 PM11/1/17
to vagra...@googlegroups.com
Hi,

Same output.

Let me try again.

Regards,
Vikas

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/7pBtMwV1ej8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezsw%3DdsB6u5ZRBYE-1Ot7ZpeU5BwrZ471XyvWZpOY1ymw%40mail.gmail.com.

Vikas Ga

unread,
Nov 1, 2017, 7:36:24 PM11/1/17
to vagra...@googlegroups.com
Hi,

No luck again.

Reinstalled latest gem and vagrant again.

same output.

Regards,
Vikas

Alvaro Miranda Aguilera

unread,
Nov 2, 2017, 4:49:31 AM11/2/17
to vagra...@googlegroups.com
hello

what do you mean by latest gem ?

you shouldn't be instally any gem for vagrant, only the binary 

Alvaro


For more options, visit https://groups.google.com/d/optout.



--
Alvaro

vikas...@gmail.com

unread,
Nov 2, 2017, 3:47:54 PM11/2/17
to Vagrant
Hi ,

I mean to say rubygems is uptodate.

Regards,
Vikas

On Thursday, 2 November 2017 03:32:16 UTC+5:30, vikas...@gmail.com wrote:

vikas...@gmail.com

unread,
Nov 4, 2017, 6:25:28 PM11/4/17
to Vagrant
Hi,

Changed the OS to Ubuntu. It is working fine now.

Thanks for the help.

Regards,Vikas


On Thursday, 2 November 2017 03:32:16 UTC+5:30, vikas...@gmail.com wrote:
Reply all
Reply to author
Forward
0 new messages