Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"panic: runtime error: slice bounds out of range" when running vagrant #41

Closed
konrness opened this issue Jun 30, 2014 · 3 comments
Closed

Comments

@konrness
Copy link

I previously had Vagrant 1.5.4 installed. I installed 1.6.3 over it and it caused this problem to happen. Then I uninstalled 1.6.3 and deleted the entire c:\HashiCorp directory and reinstalled 1.6.3 and still had this problem.

c:\HashiCorp\Vagrant\embedded\gems\gems>vagrant
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
runtime.panic(0x4a6540, 0x59180a)
        C:/Users/Mitchell/code/3rdparty/go/src/pkg/runtime/panic.c:266 +0xa6
main.main()
        c:/Users/Mitchell/code/mitchellh/vagrant-installers/substrate/launcher/m
ain.go:35 +0x19d3

This issue occurred because c:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.5.4 did not have a /lib/vagrant/pre-rubygems.rb file in it. It only has a tests directory.

Workaround: rename c:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.5.4 to a directory name that does not start with "vagrant-*", such as "vagrantx-1.5.4".

@konrness
Copy link
Author

It turns out I never actually deleted the C:\HashiCorp directory which is why there was a vagrant-1.5.4 directory in the first place. Leaving this issue open as I feel the installer should be aware of old versions of Vagrant and properly clean them up prior to installing a new version.

@piotr-cz
Copy link

piotr-cz commented Sep 7, 2014

I got this exact message after upgrading from 1.6.3 to 1.6.5 on Windows machine.
I've tried reinstalling 1.6.5 and deleting installation folder in meantime but only thing that helped was to uninstall 1.6.5 and install 1.6.3 back.

This is a duplicate of [https://github.com/hashicorp/vagrant/issues/3659]

@sethvargo
Copy link
Contributor

Hi there,

This has been fixed on master. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants