You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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".
The text was updated successfully, but these errors were encountered: