I am attempting to learn a bit about the command line and am following a free online course. I have been instructed to install a number of programs on my computer including VirtualBox, Vagrant and Git which I have done. There was a VagrantFile which I have also downloaded.
The problem I have is that Git Bash is not responding to any vagrant command. I am not familiar enough with the command line to test other programs or commands out but I have checked the Python version for example and got a response.
So when I attempt to run any vagrant command the interface returns the same location and then freezes. I can click and highlight within the window but it will not take any keyboard input. This happens regardless of whether I navigate to the vagrantfile folder or not.
Really confused! I have uninstalled and re-installed all the programs.
Currently operating:
Windows 10
Vagrant 1.9.7
Oracle VM VitualBox 5.1.26
Git 2.14.0
... MINGW64 ~
$ cd Desktop/Shell
... MINGW64 ~/Desktop/Shell
$ vagrant up
... MINGW64 ~/Desktop/Shell
$
// At this point the interface freezes and won't accept
// any input. It is the same if I call
// vagrant init
// vagrant --version
// vagrant halt --force
Any help would be hugely appreciated.
Thanks Chris.
Related
I am a beginner so please someone should show me kindness by showing me how to resolve my issue as a student. I've installed vagrant on git bash but every command seems to be telling me bash : vagrant command not found even vagrant halt is not working. please what do I do???
I wanted to install docker engine so i started by installing vagrant with git bash. Everything was successful so I tried
sudo yum install docker
The answer was: no command found
Then I tried sudo -i to get to the root and run the command again. Answer was bash : vagrant command not found
From here on all commands I try give me the same answer. I even tried to force vagrant halt but the same answer comes out.
If you receive an error that Vagrant is not found, try logging out and logging back in to your system (particularly necessary for Windows). $ vagrant Usage: vagrant [options] [] -v, --version Print the version and exit.
So I am having some issues with vagrant. I had initially tried to report this as an issue on the vagrant github issue boards, but they kept closing the issues without responding to them. I guess they decided I wasn't worth their time, or they were just behaving unprofessionally. Anyway, Here is the problem: I use vagrant with virtualbox, and a new version of virtualbox was recently released that is, unfortunately, not compatible with the latest vagrant installation.
However, the people at hashicorp have already updated the source code so that it is compatible with the new version of virtualbox, but you have to build the vagrant executable from the source repo (instructions here). So I followed the instructions and vagrant is working just like it used to.....when the only command I need to run is vagrant up. I should also mention ahead of time that, in order to run the vagrant dev build, the current working directory needs to be the root of the source code repo and the dev build can only be run using the following command with ruby:
bundle exec vagrant
With that being said, I needed to update one of my custom boxes, so I built a vm in the updated version of virtualbox and ran the below command
bundle exec vagrant package --base go --vagrantfile ../../vagrant/vagrantfile
After an extended period of time, vagrant spat back out the following error
The executable 'bsdtar' Vagrant is trying to run was not found in the %PATH% variable. This is an `error. Please verify this software is installed and on the path.`
I should also note that I use a windows machine and that this error never occurred when using the installed version of vagrant. At this point, I had posted the issue on github to get some input from the devs, but they (very unprofessionally) decided to ignore my requests for help and close the issues without providing any response. I used the GNUwin32 project to make numerous unix commands available to my Windows environment and added the folder to my PATH environment variable. I then run the same command again to create my new box and it works!! So then I upload it to the vagrant cloud and attempt to update the vagrant box that is stored on my system by running the following command:
bundle exec vagrant box update
Then, after waiting for a while, vagrant then spat this error out at me:
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and that enough disk space
is available and then try again.
The output from attempting to unpackage (if any):
C:\gnuwin32\bin/bsdtar.EXE: invalid option -- s
Usage:
List: bsdtar.EXE -tf <archive-filename>
Extract: bsdtar.EXE -xf <archive-filename>
Create: bsdtar.EXE -cf <archive-filename> [filenames...]
Help: bsdtar.EXE --help
Another error, and still involving this bsdtar tool. It does not appear that anyone else is reporting the issue I am running into because I think they are just waiting for hashicorp to release the new official installation, but, just to give you a look into their priorities, the version of virtualbox that was released which no longer worked with vagrant was released back on December 10. It has been over a month since and there is still no updated release.
So, I am hoping that someone out there might be able to find out why I keep running into these errors when trying to use vagrant's dev build and provide a solution. If not, then maybe if someone else is able to reproduce the issue and report it to hashicorp, maybe they will listen to someone else.
If you are on Ubuntu 20.04 then bsdtar was removed. Try to install libarchive-tools package.
$ sudo apt-get install libarchive-tools
I figured it out. My original hypothesis was correct: since vagrant is a tool that was built primarily to be run on linux machines, then vagrant runs in windows, the installation includes a mingw environment with all of the dependencies vagrant needs to function and which the installed vagrant executable imports into the console session when run. This why the dev build kept failing: because it was not importing this mingw environment. So, in order to fix the issue, I first cloned the vagrant source code repo from github and followed the instructions I linked to above to build the executable from the source repo. I then copied all of the files in the source repo into the following folder:
<hashicorp install folder root>\Vagrant\embedded\gems\2.2.6\gems\vagrant-<version num>
So, for me, the destination directory is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6
This directory is identical to the source code repo, and copying the source code repo to the above folder replaces the installation version of vagrant with the dev build. After I did this, running the vagrant commands which had failed previously normally (as in, without using ruby or bundle) worked. I hope this helps someone else out there who Hashicorp has decided is not worth their time.
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.
I have installed Git, VirtualBox and Vargant on my Windows 10 computer.
Have problems with starting Vargant using git-bash console.
When I do vargant init - this create vargant file and looks like it's ok.
Alex#DESKTOP MINGW64 /d/shell
$ vagrant init hashicorp/precise32
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
But when I try to start vagrant with vagrant up command I receive error.
Alex#DESKTOP MINGW64 /d/shell
$ vagrant up
bash: vagrant: command not found
I have tried restarting, reinstalling these software, installing latest or previouse versions of software - nothing helps - still bash: vagrant: command not found.
What shell I do next to solve the problem?
the command / program name is vagrant , not vargant. You spell it correctly in the init, but the rest of your examples have it spelled incorrect. Try running vagrant up and you should be all set.
I am interested in Rethinkdb and would like to develop/test on it, but main problem is: it don't have package for windows operating system. I tried to compile from source code, that was also not possible as there was no any instruction.
What makes it so difficult to make executable for windows? Is there any alternative way to install Rethinkdb in windows OS? even very small and not that famous application has windows binary but not Rethinkdb. It is quite surprise for me. Another surprising is there are many community executable for other OS but not windows.
Thank you for understanding and waiting for good answer.
Rethinkdb just announced that it started development for Windows. Please follow
[1] https://github.com/rethinkdb/rethinkdb/issues/1100
[2] https://twitter.com/segphault/status/590633792781611009
Update:
RethinkDB announced in Windows :
[3] https://rethinkdb.com/docs/install/windows/
Cross-platform development isn't that easy. RethinkDB uses some features under the covers which makes porting it to Windows a difficult job, f.e. a Unix toolchain for the builds and Unix syscalls. For more information on that have a look at this GitHub issue. It states that Windows support is planned, but with low priority.
As a quick fix, you could RethinkDB run in a virtual machine or in Microsoft Azure. For the second one, I wrote a blog post a few weeks ago.
RethinkDB has already started development for Windows. While it's not released yet, this is how you can run it through Vagrant. See: https://github.com/gearz-lab/rethinkdb-vagrant
I'm using Chocolatey, feel free to skip steps if they don't apply.
Installing Chocolatey
Open Powershell as an administrator and run this command:
iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
... now you should have Chocolatey installed. We're gonna use to install the others.
Installing Vagrant
Run this as an administrator:
choco install vagrant -y
Installing VirtualBox
Vagrant relies on a virtualization application that it calls a "provider". The default one is VirtualBox so let's install it. Run cmd as administrator and run this:
choco install virtualbox -y
Now you should be able to run the vboxmanage command. If it doesn't work, make sure C:\Program Files\Oracle\VirtualBox is in your PATH.
Installing Cygwin
We're gonna log on a virtual machine using SSH, so we need a SSH enabled terminal. For that, let's use Cygwin.
choco install cyg-get -y
Installing Cygwin packages
There'are two Cygwin packages we need to install, openssh, because Cygwin doesn't have SSH support by default, and rsync so Vagrant can use it to synchronize files between the host and the guest machines.
On PowerShell, running as an administrator, let's run these commands:
cyg-get openssh
cyg-get rsync
Cloning rethinkdb-vagrant
Open the Cygwin64 Terminal. You should now be in your Cygwin home folder, which should look like C:\tools\cygwin\home\[YOUR_USER].
Make sure you have git installed. If you don't just choco install git -y. Now, clone rethyinkdb-vagrant:
git clone https://github.com/gearz-lab/rethinkdb-vagrant.git
Now you should have a directory like this: C:\tools\cygwin\home\[YOUR_USER]\rethinkdb-vagrant.
Starting Vagrant and useful commands
From inside the Cygwin64 Terminal home directory (described in the last step), type cd rethinkdb-vagrant, now, any Vagrant commands will target cd rethinkdb-vagrant.
To setup and boot the machine: vagrant up (After this, RethinkDB is available, see next step).
To access the machine's terminal: vagrant ssh.
To destroy the machine (every RethinkDB data will be lost): vagrant destroy.
To suspend the machine: vagrant suspend.
To resume a suspended machine: vagrant resume.
Accessing RethinkDB.
Make sure you have vagrant up from the last step. Now:
For accessing the web administration tool: http://localhost:8080.
For accessing RethinkDB from a client app, the port is 28015.