Re: Accepted vagrant 2.0.2+dfsg-2~bpo9+1 (source all) into stretch-backports, stretch-backports
On Fri, Mar 23, 2018 at 07:02:02PM +0000, Aron Xu wrote:
> Version: 2.0.2+dfsg-2~bpo9+1
> Distribution: stretch-backports
Hi,
I really appreciate this upload, but somehow it seems to break for me.
Does it work for anyone and is maybe just something odd about my local setup?
$ vagrant init debian/stretch64
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.
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'debian/stretch64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'debian/stretch64'
default: URL: https://vagrantcloud.com/debian/stretch64
==> default: Adding box 'debian/stretch64' (v9.4.0) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/debian/boxes/stretch64/versions/9.4.0/providers/virtualbox.box
==> default: Successfully added box 'debian/stretch64' (v9.4.0) for 'virtualbox'!
==> default: Importing base box 'debian/stretch64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/stretch64' is up to date...
==> default: Setting the name of the VM: sven_default_1522074175656_61292
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
/usr/lib/ruby/vendor_ruby/net/ssh.rb:204:in `start': invalid option(s): verify_host_key (ArgumentError)
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:409:in `block (2 levels) in connect'
from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:383:in `block in connect'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:382:in `connect'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:83:in `block in wait_for_ready'
from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:33:in `catch'
from /usr/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:61:in `wait_for_ready'
from /usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'
Cheers,
Sven
Reply to: