Syncing folder to a user directory breaks SSH

[rvangundy]

I've got a pretty custom setup going, so this might be outside the scope of vagrant, but I figured someone here might have some experience with this kind of thing...

I've built an Arch Linux base image. I would like to synchronize my project folder with a folder in the user's home directory, such as /home/vagrant/my_project. If I mount it like this:

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

I am no longer able to SSH in. I get the following response:

ssh_exchange_identification: Connection closed by remote host

I'm able to mount any other folder outside the user's directory just fine. The /vagrant mount works as expected.

I'm wondering if there's a security-related setting I'm missing that relates to folder permissions in a user's home directory? Since this is a vagrant-y issue, maybe others building vagrant boxes have encountered this.

[canausa]

Most linuxish systems use ssh keys located in a hidden home directory
located at ~/.ssh . it is how the systems now which keys are valid for each
system. So when you mount your project to that directory it loses access to
the .ssh directory.

There are 3 solutions.

• copy the .ssh directory in to your project.
• not mount your project to the home directory of vagrant
• tell vagrant to use password authentication instead of ssh keys.

On Thu, Nov 6, 2014 at 11:33 AM, rvangundy notifications@github.com wrote:

I've got a pretty custom setup going, so this might be outside the scope
of vagrant, but I figured someone here might have some experience with this
kind of thing...

I've built an Arch Linux base image. I would like to synchronize my
project folder with a folder in the user's home directory, such as
/home/vagrant/my_project. If I mount it like this:

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

I am no longer able to SSH in. I get the following response:

ssh_exchange_identification: Connection closed by remote host

I'm able to mount any other folder outside the user's directory just fine.
The /vagrant mount works as expected.

I'm wondering if there's a security-related setting I'm missing that
relates to folder permissions in a user's home directory?

—
Reply to this email directly or view it on GitHub
#4791.

[rvangundy]

@canausa Good points. In my case I'm mounting a folder next to the .ssh folder, in /home/vagrant/project. I've done this using other base images, so I'm guessing it's a configuration issue in my image.

[Xylakant]

@rvangundy If there's an issue with directory permissions or similar you could have a look at the logfiles inside the machine. I'd start the machine with enabled gui and then the log in there (username/pw should be vagrant/vagrant) and observe the logs while trying an ssh login. This should give you an idea where to look.

edit: sorry for the initially wrong mention :(

[mitchellh]

Yes, @canausa is correct. We do some detection to detect this but it isn't 100%. Don't sync to your home folder. :)

[domenkozar]

Hmmm, unpleasant. Couldn't .ssh be installed/created after synced folders are mounted?

[nakulpathak3]

Ran into same issue today