thomastthai
commented
11 months ago The vagrant@127.0.0.1: Permission denied (publickey) error is a common issue per Google search.
Vagrant insecure key detected appears to be a normal warning. However, that didn't help get through to the next step. What helped was the following:
After vagrant halt && vagrant destroy, adding config.ssh.insert_key = false to Vagrantfile helped get through this error.
Thomas@Sammy MINGW64 ~/development/rpi-cloud-init (main)
$ cat Vagrantfile
$script = <<-SCRIPT
curl -sL get.hashi-up.dev | sudo sh
sudo hashi-up packer get --version 1.9.4 -d /usr/local/bin
SCRIPT
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/focal64"
config.ssh.insert_key = false
config.vm.boot_timeout = 600
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uartmode1", "disconnected" ]
end
config.vm.provision "shell", inline: $script
endFeel free to close this issue once you review it.
Platform: Windows 11, AMD64 Git Bash CLI
To get Vagrant to use the included SSH instead of Window's version:
$ export VAGRANT_PREFER_SYSTEM_BIN="0" && echo $VAGRANT_PREFER_SYSTEM_BIN 0The error appears at the end of this report. What may be related are these lines earlier in execution:
The whole execution log: