Closed bbethell closed 7 years ago
New Issue now instead....
Virtual box version is too old, even though it is on 5.1
@bbethell What does vboxmanage --version
say?
Hi,
it says error while loading shared libraries: VBoxRT.dll no such file or directory?
I have VBoxManage in my vagrant/bin directory
Thanks
Billy
-------- Original message -------- From: Steffen Hanikel notifications@github.com Date: 28/06/2017 16:38 (GMT+00:00) To: flix-tech/vagrant-kubernetes vagrant-kubernetes@noreply.github.com Cc: bbethell billybethell@hotmail.co.uk, Mention mention@noreply.github.com Subject: Re: [flix-tech/vagrant-kubernetes] Issue with Syntax (#6)
@bbethellhttps://github.com/bbethell What does vboxmanage --version say?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/flix-tech/vagrant-kubernetes/issues/6#issuecomment-311699207, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYAMgMJJxCNZyMn9FOAZqDGX1DlBaQjJks5sInOBgaJpZM4OGqKe.
I experienced the same issue when upgrading box from 1.5.1
to 1.6.4
. On Windows 10 I would get the exact same error that @bbethell got. When I tried vboxmanage
on PowerShell it said no such command. Once I added VirtualBox installation to Path
and restarted PowerShell everything worked fine. I am not sure what fixed it.
There was an error loading a Vagrantfile. The file being loaded and the error message are shown below. This is usually caused by a syntax error.
Path: C:/Users/bbethell/.vagrant.d/boxes/flixtech-VAGRANTSLASH-kubernetes/1.6.4/virtualbox/Vagrantfile Line number: 0 Message: Errno::ENOENT: No such file or directory - vboxmanage --version