I have a cluster of 3 VMs. Here is the Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
hosts = {
\"host0\" => \"192.168.33.10\",
\"host1\" =&
Vagrant changed the behaviour between 1.6 and 1.7 versions and now will insert auto generated insecure key instead of the default one.
You can cancel this behaviour by setting config.ssh.insert_key = false
in your Vagrantfile.
Vagrant shouldn't replace insecure key if you specify private_key_path
like you did, however the internal logic checks if the private_key_path
points to the default insecure_private_key
, and if it does, Vagrant will replace it.
More info can be found here.