Invalid gemspec in [.......]: stack level too deep #9788
Comments
|
Hi there, This looks like a problem with your Vagrant installation. The specification warnings from the rbnacl-libsodium gemspec are not associated with Vagrant. How did you install Vagrant? Please also provide a gist of the output from: Thanks! |
|
Hey please will somebody give the answer for this question , I am having same problem too. here is the ouput of the vagrant box list --debug Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-libsodium.gemspec]: stack level too deep |
|
here you are: Thanks! |
|
any update on topic !? Thanks |
|
Heys Guys I found a solution, Just update your vagrant that works. Download direct from the vagrant website and don't use the version of ubuntu repository (apt-get install vagrant). The ubuntu version is outdated. |
|
Hi there, @egonyuri is correct. Using the installer from the downloads page will resolve this issue. I'm not sure how you have Vagrant installed, but it does not appear to be from the official installers. Cheers! |
|
thanks @egonyuri That solved it 👍 😄 |
|
3 months later it still solved it @egonyuri : you rock. |
|
Same here, using Vagrant from Ubuntu repository, and it crashes with above error. It's good that your non-Ubuntu installer works, but you should be wary of supporting the Ubuntu packages as well (or remove them from the archive). |
|
Hey @VickySteeves - sorry the Ubuntu packages are broken! Unfortunately we at HashiCorp have no control over what version of Vagrant Ubuntu ships with, and therefore is not officially supported by us. |
|
It looks like it's affecting vagrant shipped in debian |
|
Currently it looks like Hashicorp packages are also broken. Neither installation works, the Ubuntu packages actually seem less broken at the moment. because it's at least trying with the stack level too deep error. The hashicorp package just says it finds no vagrant executable. |
|
@ginsburgnm Hi there. The current release of Vagrant functions as expected on Ubuntu. I just spun up a fresh system to validate: If you are having issues, ensure that any vagrant package is fully uninstalled and then install the official package again. It may be that a Cheers! |
|
@chrisroberts $:wget -q https://releases.hashicorp.com/vagrant/2.2.0/vagrant_2.2.0_x86_64.deb --EDIT-- |
|
@ginsburgnm - Installing Vagrant 2.2.0 works for me on Ubuntu 18.04.1 LTS: |
|
I'll just assume there's a conflict with something my org is doing. because, same version of vagrant and ubuntu. different results. |
|
@ginsburgnm The output you provided above shows this path in the error message: which then goes on to mention the path: The Vagrant executable at |
|
@chrisroberts that was exactly it. |
|
I created a bug in Ubuntu bug tracker: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1804626 |
|
In my case this was caused by trying to install Vagrant from source on an Ubuntu 18.04 system, and then abandoning that attempt and trying to go back to the regular Ubuntu Vagrant. I think that installed a bunch of extraneous Ruby gems that caused conflicts with the regular Ubuntu Vagrant. The way I found these incompatible gems is by running this command to find gems not tracked by the package manager:
This told me I had a whole bunch of untracked gems under |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Hi Vagrant Team,
Vagrant version
Vagrant 2.0.2
Ruby version
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]
Host operating system
Linux kali 4.15.0-kali2-amd64 #1 SMP Debian 4.15.11-1kali1 (2018-03-21) x86_64 GNU/Linux
I upgraded Kali to the last changes via
dist-upgradeandupgradewith "apt-get" command.Vagrantfile
as default. without modification.
Virtualbox
VirtualBox Graphical User Interface Version 5.2.8_Debian r120774
© 2004-2018 Oracle Corporation (Qt5.9.2)
behavior
Why the list is empty !??
Why I got this error or warning message for every vagrant command !?
How to fix it !?
Thanks in advance
The text was updated successfully, but these errors were encountered: