Installed version: N/A - laravel

Help solve the problem with powershell.
I use as a console git bash. VT-x enabled. Hyper-v disabled.
Problem in
The version of powershell currently installed on this host is less than
the required minimum version. Please upgrade the installed version of
powershell to the minimum required version and run the command again.
Installed version: N/A
Minimum required version: 3
Installed powershell 6.
The error usually occurs when entering
vagrant ssh
or
vagrant up
It's funny that the problem is solved by re-entering vagrant up or vagrant ssh.
What is the problem ?
p.s. Sorry for bad English :)

The comment by Theo solved the issue for us.
powershell -Command 'vagrant up'
Executing vagrant ssh next works as expected AND is also a little faster.

Related

ElasticsearchException: Failure running machine learning native code

i am learning Elasticsearch and tried to install it on my windows 8 (64 bit) machine.
firstly i tried to install in using zip file downalod elasricsearch
but that didn't worked for me, the command prompt gets closed after this
after that i tried installing elasticsearch using windows installer (MSI).
but i ended up having this
i found one cause for this error on internet that environment is not 64bit but in my case it is..please give me some sollution.
you can append a config line
xpack.ml.enabled: false
in config file ${elastic_search_home}/config/elasticsearch.yml to bypass this problem.
In case you run in Docker container you can disable machine learning functionality setting environment variable -e "xpack.ml.enabled=false".
For Mac Users
On OSX installed with Homebrew
Add: xpack.ml.enabled: false
To: /usr/local/etc/elasticsearch/elasticsearch.yml
And restart: brew services restart elastic/tap/elasticsearch-full

Vagrant up problem: sh: netsh: command not found

I am using macOS Mojave. After I installed VirtualBox and Vagrant, I tried "vagrant up". However, I got following strange error:
Dir: VA $vagrant up
sh: netsh: command not found
sh: cscript: command not found
It seems that you don't have the privileges to change
the firewall rules. NFS will not work without that
firewall changes. Execute the following commands via
cmd as administrator:
netsh advfirewall firewall add rule
name="VagrantWinNFSd-1.4.0" dir="in" action=allow
protocol=any
program="\Users\Ten\.vagrant.d\gems\2.4.4\gems\vagrant
...
It seems netsh and cscript command belong to Windows. However, I am using macOS and I am sure my VirtualBox and Vagrant are for macOS.
Can any one help me with this question? Thanks!
===================== Updated ===================
At last I solved this problem. However I am sorry I forgot I raised the question here and even worse I forgot how I solved it.
The only thing I remembered is, installing VirtualBox first and then Vagrant is important. And reinstallation may help.
Hope this can help a bit.
I faced this issue on macOS Sierra (10.12.6). I resolved it after finding that I had the plugin vagrant-winnfsd installed.
To uninstall, I ran the command:
vagrant plugin uninstall vagrant-winnfsd

No output using vagrant Windows 10

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.

error when using "vagrant box add laravel/homestead" on OSX

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

Failed to find Vagrant

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

Resources