› vagrant -v
Vagrant 2.2.4
› ruby -v
ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
Arch Linux, Kernel 5.0.0
Debian 9 (via debian/contrib-stretch64 v9.8.0)
Vagrant.configure('2') do |config|
config.vm.box = 'debian/contrib-stretch64'
config.vm.define 'test' do |cfg|
end
end
https://gist.github.com/Lavode/3f1a260c654146b931839275eb1d670f
Vagrant should spawn the machine - or provide a useful error message if something goes wrong.
Exception thrown within net-sftp library.
vagrant up2.2.3 fixed the issue.I'm having the exact same issue since upgrading
here's debug log of a very single ubuntu vagrant that fails
Vagrant.configure("2") do |config|
config.vm.box = 'ubuntu/xenial64'
config.vm.network :private_network, ip: '33.33.33.25'
config.vm.provider 'virtualbox' do |vb|
vb.gui = false
vb.memory = '2048'
end
end
https://gist.github.com/ssherman/ae3d91bd2e0d04e4f30049f373a5ed97
I downgraded to 2.2.2 and everything works again, so this is definitely a 2.2.3 or 2.2.4 issue.
The origin of the error is quite odd. It's happening while the net-sftp library is loading, however since the sftp upload option was never used (since it required as many manual steps as the required scp updates) we can just remove the loading.
I had to downgrade to 2.2.2 too because of this issue. Here's how to install 2.2.2 on macos:
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask/
git log master -- Casks/vagrant.rb
# this will give you the hash of the 2.2.2 version
# then just install
vagrant_hash=51a87e70b29adb6efc9f85c54b1f6c163955c0ae
brew cask install https://raw.githubusercontent.com/caskroom/homebrew-cask/${vagrant_hash}/Casks/vagrant.rb
:v: Thanks
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Most helpful comment
The origin of the error is quite odd. It's happening while the net-sftp library is loading, however since the sftp upload option was never used (since it required as many manual steps as the required scp updates) we can just remove the loading.