I'm not sure if this belongs her or another site, so let me know and I'll remove it if not. So I'm attempting to install vagrant on a windows 10 machine. I have virtual box installed, I have a kali linux machine on it that I've used in the past. After using the msi to install vagrant, I rebooted as prompted. After reboot I verified vagrant was added to the path.
Issuing any vagrant command shows nothing in the output. I've tried passing -h and --version and nothing shows. Even running as admin and powershell gives no response. No hanging or freezing, just nothing in the response. Not even a command not recognized warning(more validation its in my path).
Can anyone help me find out whats going on and why none of the vagrant commands seem to respond?
OUTPUT EXAMPLE
C:\>vagrant init -h
C:\>vagrant --version
C:\>
im guessing its something to do with their latest 1.9.7 version? i installed 1.9.6 and it finally gives me some output.
Related
First of all I'm sorry if someone already did this question, in this case please paste the link here because I didn't find anything.
I'm learning vagrant, using virtualbox i don't have problem in running VM, but if I would like to use VMware as provider. I encounter this message and I can't find a way to get out of this.
I think everything is well configured but obviously something is wrong.
When I launch vagrant up --provider=vmware_desktop, I have this error message:
Vagrant encountered an unexpected communications error with the
Vagrant VMware Utility driver. Please try to run the command
again. If this error persists, please contact support#hashicorp.com
I'm currently using Fedora 35
Operating System: Fedora Linux 35 (Workstation Edition)
Kernel: Linux 5.17.5-200.fc35.x86_64
Architecture: x86-64
I have followed this thread:
https://github.com/hashicorp/vagrant-vmware-desktop/issues/22
and someone had prepared a nice gist -- which I copied below just in case the gist link wasn't anymore.
My issue was mainly the Vagrant 2.2.19 which somehow was not ok with VMWare. 2.2.18 worked fine. Just make sure you follow the above gist step by step.
https://gist.github.com/sbailliez/f22db6434ac84eccb6d3c8833c85ad92
My issue was mainly the Vagrant 2.2.19 which somehow was not ok with VMWare. 2.2.18 worked fine. Just make sure you follow the above gist step by step.
Vagrant and VMWare Tech Preview on Apple M1 Pro
This document summarizes notes taken while to make the VMWare Tech preview work on Apple M1 Pro, it originated
from discussions in https://github.com/hashicorp/vagrant-vmware-desktop/issues/22
Installing Rosetta
First install Rosetta if not already done, this is needed to run x86 code:
/usr/sbin/softwareupdate --install-rosetta --agree-to-license
Installing Vagrant
Install Vagrant via brew or install it manually. Note that I use 2.2.18 as 2.2.19 did not work for me. (YMMV)
brew install vagrant#2.2.18
Installing VMWare Fusion Tech Preview
You will need to create an account on vmware as it needs user and key information that are user specific.
The registration process is kinda convoluted. Be careful about passwords as the password needs to be less than 20 characters and there are no error messages for this.
You can download the tech preview via the download page.
Once this is installed you will NEED to create a symlink as the vagrant vmware utility etc.. assumes that vmware is installed in a specific directory and the tech preview is installed in a different one.
ln -s /Applications/VMWare\ Fusion\ Tech\ Preview.app /Applications/VMWare\ Fusion.app
Installing Vagrant VMWare provider
It requires two steps. This is detailed in the documentation but follow the steps below:
First go to Vagrant vmware Utility and download the binary and install it. It says x86_64 but it is fine.
The direct link is:
https://releases.hashicorp.com/vagrant-vmware-utility/1.0.21/vagrant-vmware-utility_1.0.21_x86_64.dmg
It needs to be version 1.0.21
Next install the provider:
vagrant plugin install vagrant-vmware-desktop
Create a Vagrant file
Create a file Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "spox/ubuntu-arm"
config.vm.box_version = "1.0.0"
end
Run vagrant
vagrant up
and then
vagrant ssh
Hopefully this should work and you should find yourself with mostly everything working.
Troubleshooting
I have observed various issues that makes the whole experience unstable or creating conflicts.
vagrant 2.2.19 is broken
I have had issues trying to run vagrant 2.2.19. Use 2.2.18
vagrant-vmware provider forwarded ports bound
If you declare forwarding port on your box, for some reasons the provider persists them and keeps it bound in LISTEN state even after you do a vagrant halt.
You can check this using something like:
sudo lsof -i -P | grep LISTEN | grep 'vagrant-v'
You can see the ports are stored in:
cat /opt/vagrant-vmware-desktop/settings/portforwarding.json
To stop the provider use:
sudo launchctl unload -w /Library/LaunchDaemons/com.vagrant.vagrant-vmware-utility.plist
To start it again, use load instead of unload.
nfs exports conflicts
If your vagrant box uses nfs, it seems to pollute the /etc/exports file with duplicate or stale entries over time which will cause vagrant to get angry at you at some point. You may need to prune the entries. It seems related to vagrant#11418
I encountered this same issue you had with the architecture compatibility while trying to set up VM on my Mac M1. Found my solution in this GitHub thread
I just added this lines to the Vagrantfile
config.vm.provider :vmware_desktop do |v|
v.vmx["ethernet0.pcislotnumber"] = "160"
end
I installed vagrant (vagrant_1.9.7_x86_64.msi) and have installed VirtualBox (VirtualBox-5.1.24-117012-Win) on a Windows 10 64-bit system.
I have verified that all PATH settings are fine. Completely removed both Vagrant and VirtualBox (also the .vagrant.d folder) and re-installed both.
When in a command-box I do something like vagrant or vagrant --version, nothing happens, no error, just the command prompt on the next line. Strange thing though is, this has worked at one point. It was when I tried to install Homestead for a laravel project and it was pointed out that I should update Vagrant when thing were going wrong.
Anyone with a similar experience?
I am trying to add the laravel/homestead box to my vagrant installation and keep getting the error "The program 'vagrant' is currently not installed. You can install it by typing: sudo apt-get install vagrant"
I have virtual box installed and working (I use it regularly) and I just downloaded vagrant and it DID say it downloaded successfully. Some forums suggest my installation is not up to date but I installed it about 15 minutes ago so I don't think that could be the case.
Also, I have already created a new directory using mkdir, then used "vagrant init hashicorp/precise32" and then "vagrant ssh" which have all been successful. The next thing I try to do is add the box and it won't work. I have never used vagrant before so I am unfamiliar with this. Any help is appreciated!
PS I'm on OSX El Capitan
Not sure if this is useful after so many months, but I ran into this same problem yesterday. There appears to be a lot of information about this in the vagrant git forums.
As a workaround (not fix) I downgraded to virtualBox 5.0, and vagrant 1.7.4
not sure why I'm having this issue but I can't add vagrant boxes.
Using windows 10, tried on powershell and simple command prompt. same issue. It's a relatively fresh install of windows. Maybe I'm missing some required package?
first i tried this command:
vagrant box add hashicorp/precise32
and got the error:
The box 'hashicorp/precise32' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://atlas.hashicorp.com/hashicorp/precise32"]
Error:
So I downloaded the box manually and tried this:
vagrant box add base64 file:///D:/downloads/vagrant_boxes/precise64.box
And got this error again:
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'base64' (v0) for provider:
box: Unpacking necessary files from: file:///D:/downloads/vagrant_boxes/precise64.box
box:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The libraries on current version (as of this date) OSX don't support the version of curl bundled with Vagrant 1.8.7. I installed 1.8.6 and everything worked like a champ. To test this theory:
cd /opt/vagrant/embedded/bin
./curl --help
If you get a 'normal' reply than you should be fine or there's something else wrong.
I was using vagrant v1.8.0 when this happened. Later that day vagrant v1.8.1 was released. I didn't try that, instead I shifted back to v1.7.4 and the issue was gone.
I've been resolving this issue since I installed vagrant 1.8.1, I tried to installed lower version but i came up with the same problem. Hopefully, I solve it here:
first make sure you installed Microsoft Visual C++ 2010 SP1 Redistributable.
here is for 64bit https://www.microsoft.com/en-us/download/details.aspx?id=13523
next, download ssl version of curl in my case 64bit also. here:
https://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi
now extract the curl.exe to C:\Vagrant\embedded\bin. please see your installation directory.
and then done. if your not using ssl try the no-ssl version of curl. hope helps
Check the C: \ HashiCorp \ Vagrant \ embedded \ bin \ curl.exe
case give an error, there is your problem.
To solve, just download gitbash, console2, cmder, etc ... you have curl installed, or try http://www.confusedbycode.com/curl/.
however strongly recommend gitbash or cmder
https://atlas.hashicorp.com/hashicorp/boxes/precise32
base on the offical URL.. there is only virutal box provider.
try below command:
vagrant init hashicorp/precise32; vagrant up --provider virtualbox
For MacOS users whom reinstalling new version of vagrant doesn't help:
sudo mv /opt/vagrant/embedded/lib/libiconv.2.dylib /opt/vagrant/embedded/lib/libiconv.2.dylib_
brew install libiconv
brew link --force libiconv
credits to: https://github.com/mitchellh/vagrant/issues/5782
You don`t need to add the box. Init instead of this:
vagrant init hashicorp/precise32
vagrant up
vagrant ssh
Hope it will be added in boxes list automatically.
If you want to set up local box - add it getting few steps:
D:
cd downloads/vagrant_boxes
vagrant box add base64 precise64.box
vagrant up
vagrant ssh
Trying to install Vagrant on Windows 7 X64 with installer from Vagrant - vagrant_1.7.0.msi
Installation goes fine, however unable to use vagrant. On any command, for example vagrant -v the below is shown:
Failed to find Vagrant!
What I did:
Googled. Only 1 link with such an error on github regarding to installer. Not sure if this is relevant.
Checked that vagrant in PATH. Yes it is. Otherwise it would not start at all.
Reinstalled, and repaired - few times.
All the above with no luck. Any idea where to dig?
Thank you.
just to add my own version of this problem too:
i installed version 1.7.0
error message after a "vagrant up": "Failed to find Vagrant!"
checked paths, other environment variables in win7, should work..
so i uninstalled it and installed an older version (1.6.5)
and yes, the older version solved the problem.
i got it from their official website: https://www.vagrantup.com/download-archive/v1.6.5.html
i guess the problem was in this file:
https://github.com/mitchellh/vagrant-installers/blob/master/substrate/launcher/main.go
Same Issue on Windows 7 64.
Downgraded back to Vagrant 1.6.5
Have you gone through the installation instructions on vagrant side listed here :
https://docs.vagrantup.com/v2/installation/index.html
This is what I see listed at their site:
The installer will automatically add vagrant to your system path so that it is available in terminals. If it is not found, please try logging out and logging back in to your system (this is particularly necessary sometimes for Windows).
Please try running it from Git Bash too and let me know if it works for you.
And if you still run into issues, try using an older version of vagrant https://www.vagrantup.com/download-archive/v1.6.5.html
Vagrant 1.7.1 should fix this. https://github.com/mitchellh/vagrant/issues/4924#issuecomment-66808666