Issue using Vagrant SSH when vagrant.d folder is on an external exFAT drive

Question

Setting up Vagrant for the first time and I'm using the VAGRANT_HOME environment variable to change the location of the ~/.vagrant.d folder to an external drive (I'm paranoid about SSD wear and tear, sue me). This is causing an issue with the vagrant ssh command as it's complaining about not having the right permissions and I can't use chmod to change the permissions for the file it wants on an exFAT volume.

Is there a workaround? I've checked the documentation and there doesn't seem to be a setting where I can specify a different location for the insecure key, but I might be missing something.

Thanks!

this is more a question for [superuser](https://superuser.com) — Epicblood, Jun 01 '15 at 22:32
What do you think of using a symbolic link? To move that folder to another physical location, without changing any env vars — bakkal, Jun 01 '15 at 22:34
@bakkal Creating a symbolic link at `~/.vagrant.d` pointing to the external location gives the same error. — user41997, Jun 02 '15 at 12:52

score 2 · Answer 1 · answered Jun 02 '15 at 13:17

2

The solution is to move the insecure_private_key file located in the external vagrant.d folder to somewhere in your local home directory and then symlink it back.

answered Jun 02 '15 at 13:17

user41997

2,751
2
12
12

Not my question, but ran into a similar situation. this solution worked – Casper Wilkes Aug 08 '20 at 16:49

Issue using Vagrant SSH when vagrant.d folder is on an external exFAT drive

1 Answers1