You at least need ‘rsync’ and ‘ssh’ in your path as well. Make sure your SSH and rsync clients are configured properly and in your path.įor all of this to work, you need more than just ‘vagrant’ in your path. You can do this by opening PowerShell as an administrator and typing: vagrant plugin install vagrant-vbguest Make sure VirtualBox Guest Additions are installed if you are using VirtualBox. Some other gotchyas that can bite you while running Vagrant on Windows If ($_ -match $pattern) | sc $helper_path $add = "chmod 0600 ~/.ssh/authorized_keys" $pattern = "mv ~/.ssh/authorized_keys.tmp ~/.ssh/authorized_keys" This will get you by until 1.8.6 comes out. Here’s a quick PowerShell snippet to fix the issue using method ‘c’: $pub_file = "C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.8.5\plugins\guests\linux\cap\public_key.rb" Solution Summary: Any of the above a, b, or c work, but I would suggest ‘c’ as you are guaranteed to only need to make the change one time. Or there is option d) go back to Vagrant 1.8.4, which has its own issues. You can either a) login to the VM manually by launching the GUI, and then doing a chmod on the necessary file (see the link I posted for the change that needs to be made), b) add the line “_key = false” in your Vagrantfile (if this is not set, it defaults to ‘true’), or c) edit the public key Ruby file as explained here. It will be fixed in 1.8.6, or you can fix it yourself. It’s simply an issue with the wrong permissions being applied to the ~/.ssh/authorized_keys file. This is a well known issue with version 1.8.5. Retrying…” repeat until it fails/times out. ![]() ![]() Yup - you see the VM booting and then you see “default: Warning: Authentication failure. Scenario: I just installed Vagrant 1.8.5 and now SSH isn’t working. If it was enabled, you will need to restart before VirtualBox will work properly. To disable Hyper-V (just the platform), run the command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V To check if Hyper-V is enabled, either navigate to “Turn Windows features on or off” or open PowerShell as an administrator and run the following: (Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V).State Update VirtualBox if you still have issues. You can have the Management Tools installed, just not the platform. If you are still having issues, then make sure you have a fairly recent version of VirtualBox installed as some of the older versions also seem to have issues with the anniversary update. Who knows, but disabling Hyper-V seems to fix it for most people. Some people think that it broke due to the added support for nested virtualization with Hyper-V which did come with the anniversary update. Likely this means you have a combination of 2 things going on: You are using VirtualBox as your provider AND you have Hyper-V enabled. Scenario: I just got the Windows 10 Anniversary Update, and now running when I “vagrant up” my host machine blue-screens! For simplicity, this whole post assumes that Vagrant was installed to ‘C:\’. There’s a few cases where I mention specific paths. This post is meant to help out people who may be running into issues by providing a couple of potential solutions to some of the most common issues. ![]() ![]() Getting Vagrant working properly on Windows can be a pain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |