Open bmml1 opened 5 years ago
hmm, this is not an issue of vagrant or config. this is default behavior of ssh. Not sure if there is an easy solution. Made a short search, potentially these 2 articles are of interest:
So
if argSshKey
config.ssh.private_key_path = [argSshKey, "~/.vagrant.d/insecure_private_key"]
config.ssh.insert_key = false
end
What do you think ?
Hello,
the installations works like a charm, but since FAT32 does not support file permission there seems to be a problem with accessing the private key when connecting. Copying the private key somewhere to your homefolder and then specifying the path works.
F:\Vagrant>vagrant ssh -c "sudo /vagrant/scripts/install_addons.sh" vagrant@127.0.0.1: Permission denied (publickey).
ssh -i c:\users\<user>\.ssh\private_key_vagrant vagrant@127.0.0.1 -p 2222