password - `ssh` ejecutable no encontrado en ningún directorio en% PATH%
vagrant ssh password (6)
Agregando C:/Program Files/Git/usr/bin a la variable de entorno PATH.
Añádalo manualmente o creo que puede ejecutar esto en cmd:
set PATH=%PATH%;C:/Program Files/Git/usr/bin
actualizado de los comentarios de @Ygor Thomaz
o (64 bits)
set PATH=%PATH%;C:/Program Files/Git/usr/bin
Si esto no soluciona su problema, revise:
ERROR:
c:/Users/dhawal.vora>vagrant ssh
`ssh` executable not found in any directories in the %PATH% variable. Is an
SSH client installed? Try installing Cygwin, MinGW or Git, all of which
contain an SSH client. Or use your favorite SSH client with the following
authentication information shown below:
Host: 127.0.0.1
Port: 2222
Username: vagrant
Private key: c:/Users/dhawal.vora/.vagrant/machines/default/virtualbox/private_key
Amablemente ayuda ???
El archivo Vagrant está debajo-
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don''t change it unless you know what
# you''re doing.
Vagrant.configure(2) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "precise32"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline <<-SHELL
sudo apt-get install apache2
# SHELL
end
Alternativamente, puede instalar openssh desde here y luego puede agregar ssh.exe a su RUTA mediante:
set PATH=%PATH%;C:/Program Files (x86)/OpenSSH/bin
o
set PATH=%PATH%;C:/Program Files/OpenSSH/bin
Con Windows 10 tampoco pude hacer funcionar la opción ''establecer RUTA''. Pero cuando enmendé la variable PATH a través de System Settings e inicié un nuevo símbolo del sistema, funcionó bien.
Además, la masilla funcionó perfectamente después de leer la pantalla que me indicaba que usara un nombre de usuario de ''core''.
''core'' era un requisito de mi configuración que intentaba lanzar CoreOS.
En mi caso, incluso agregar ssh al PATH no resolvió el problema. Lo que tuve que hacer es conectarme a vagabundo con ssh de forma manual. Después de ejecutar vagrant, en lugar de ejecutar vagnt ssh, hago esto:
ssh [email protected] -p 2222
Y la contraseña es "vagabunda"
Para obtener toda la información sobre la ip, el puerto y el usuario, puede usar
vagrant ssh-config
Ope esto ayuda a alguien ...
Este tutorial ilustrativo bien escrito ofrece una gran visión general sobre las formas de configurar Vagrant SSH. La primera forma es a través de Git y la segunda forma describe cómo usar Putty. Es muy fácil de seguir.
No funcionó para mí agregar C: / Program Files / Git / usr / bin a la variable de entorno PATH. Así que configuré PUTTY para la conexión ssh.