Changing Vagrantfile causes "vagrant ssh" to prompt for a password?

ssh vagrant vagrantfile
Tommy picture Tommy · May 12, 2014 · Viewed 13.1k times · Source

I've been playing around with setting up an environment using Vagrant, and I'm having an issue with the vagrant ssh command.

When I change the path of the mounted share folder in the Vagrantfile, and do a vagrant reload, I'm no longer able to vagrant ssh without it asking me for a password.

This was my original configuration for a mounted share, which works:

config.vm.synced_folder "./", "/home/vagrant/shared"

This is what I was trying to change to and it doesn't work after vagrant reload (asks me for password):

config.vm.synced_folder "./", "/home/vagrant"

Everything else in the file remained unchanged. Any idea what's going on here?

Answer

cOp picture cOp · May 21, 2014

Take note of what is actually happening here. When you share the /home/vagrant folder the VM Provider (most likely VirtualBox) has control of that folder and the permissions get all mangled by VirtualBox. You won't be able to set the 0700 perms for the .ssh folder nor will you be able to set the 0600 perms for the authorized_keys file inside the .ssh folder. Consequently, the vagrant ssh command will explicitly ask you for the password since it can't check the public key in the .ssh folder.

Makio was right about /vagrant being the default share folder. You can share pretty much any folder you want except for the /home/vagrant folder. I know about this personally because I ran into the very same issue you did. By allowing Vagrant to control the /home/vagrant folder, the permissions get set appropriately for vagrant ssh to function properly.

Glad it's resolved and I hope I shed a bit more light on exactly why this gives people a problem.

c0p

Related questions

Vagrant ssh authentication failure

The problem with ssh authentication: ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: bridged ==> default: Forwarding ports... default: 22 =&…

Read More
Can't ssh to vagrant VMs using the insecure private key (vagrant 1.7.2)

I have a cluster of 3 VMs. Here is the Vagrantfile: # -*- mode: ruby -*- # vi: set ft=ruby : hosts = { "host0" => "192.168.33.10", "host1" => "192.168.33.11", "host2" => "192.168.33.12" } Vagrant.configure("2") do |config| config.vm.box = "precise64" config.vm.box_url = "http://…

Read More
Vagrant's Ubuntu 16.04 vagrantfile default password

I'm attempting to deploy and run an Ubuntu 16.04 VM via Vagrant 1.9.1. The Vagrantfile I'm using is from Atlas: Ubuntu Xenial 16.04 Vagrantfile I'm using Debian Stretch as the host OS. Vagrant was installed via a .deb available from Vagrant's website. The …

Read More