Vagrant SSH Agent Weiterleitung + Provider Config = Fehler?

Question

Relative Vagrant und Ruby Newb hier. Ich versuche, SSH-Weiterleitung von meinem Windows-Rechner zu meinem Vagrant Ubuntu VM zu aktivieren. Meine Vagrantfile hat einige Virtualbox-Provider spezifische Konfiguration:

config.vm.provider "virtualbox" do |v| 
    v.name = guestHostname 
    v.memory = 8192 
    v.cpus = 2 
    v.customize ["modifyvm", :id, "--vram", "128"] 
    v.gui = true 
    end 

Funktioniert gut für sich. Aber wenn ich hinzufügen die Config für SSH Forwarding:

config.ssh.forward_agent = true 

Running 'vagabundierende up' beginnt mit dieser Fehlermeldung Fehler:

Bringing machine 'development' up with 'virtualbox' provider... 
==> development: Importing base box 'bento/ubuntu-16.10'... 
==> development: Matching MAC address for NAT networking... 
==> development: Checking if box 'bento/ubuntu-16.10' is up to date... 
==> development: Setting the name of the VM: development 
==> development: Clearing any previously set network interfaces... 
==> development: Preparing network interfaces based on configuration... 
    development: Adapter 1: nat 
==> development: Forwarding ports... 
    development: 22 (guest) => 2222 (host) (adapter 1) 
==> development: Running 'pre-boot' VM customizations... 
==> development: Booting VM... 
==> development: Waiting for machine to boot. This may take a few minutes... 
    development: SSH address: 127.0.0.1:2222 
    development: SSH username: vagrant 
    development: SSH auth method: private key 
==> development: Forcing shutdown of VM... 
==> development: Destroying VM and associated drives... 
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `block (2 levels) in negotiate!' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in `loop' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in `block in negotiate!' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in `loop' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in `negotiate!' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:32:in `initialize' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in `new' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in `initialize' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in `new' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in `start' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:397:in `block (2 levels) in connect' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:371:in `block in connect' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/retryable.rb:17:in `retryable' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:370:in `connect' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:68:in `block in wait_for_ready' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:46:in `wait_for_ready' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call' 

den Provider spezifische Konfiguration der Fehler macht weggeht Kommentar aus, und Spedition scheint zu funktionieren. Irgendwelche Ideen zu was könnte das Problem verursachen?

Answer 1

Ich kann sehen, dass Sie vagrant 1.9.4 verwenden, und das ist ein bekanntes Problem mit Landstreicher 1.9.4. Ich verbinde hier die github issue mit diesem Problem verbunden. Dies wurde jedoch in Version 1.9.5 behoben. So können Sie entweder auf 1.9.3 herunterstufen oder auf 1.9.5 upgraden