-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Host: Windows + git bash running vagrant leads to line ending confusion and two dozen UAC prompts while trying to change the hosts file #282
Comments
- Probably an universal solution for the line ending problem: Read the file, ignore how it converted line endings and just convert it to universal newline, then work on it also using just universal newlines. Comparison of old and new content then works. Finally, just write the file using universal newlines on all systems except Windows, where we convert to CRLF
Something's still not right there...I'll check... |
Okay, so I updated the PR with another commit. Now differences between files are checked at the correct spot. This leaves me with a lot less UAC prompts, but
|
My Vagrantfile:
My Vagrant plugins:
|
I deinstalled the other Vagrant plugins, and even with only vagrant-hostmanager installed, the above is the same. I even got 4 UAC prompts instead of 2. |
So...what can I do to help integrate the PR for the UAC part of the issue? |
Hi @danowar2k, we're reviewing this issue and your PR, stay tuned. |
After recent upgrade to OS: Win10 Pro x64 10.0.19043 Plugins:
|
Same problem for me since update to latest Virtualbox / Vagrant/ Windows 10 x64 21H1 within Hyper-V mode.
but "only" 16 times for me and it's independet if I use bindfs or not:
|
Just ran into the same problem of it getting stuck in a loop after running
Unsure if I managed to skip out of it spamming escape and ctrl+c or if it sorted itself out Vagrant: 2.2.19 |
Just ran into the same issue on Git Bash when running
Just clicked 'no' and it stopped the loop. Confirming that the first UAC deletes the host file entry, but all the others are looping for no reason.
Vagrant: 2.2.19 |
#171 isn't fixed (anymore?) in 1.8.9 but maybe it's another cause, so here we go...
vagrant destroy VMNAME
started in git bashCause:
This led to two dozen UAC prompts for writing to the system directory containing the hosts file.
Why that is happening now I can't say. As Ruby hasn't the reputation of having a very stable API, maybe Vagrant had an update of the embedded Ruby version (2.6.7 in Vagrant 2.2.16) and the Pathname.read function now works slightly different than before...but I only discovered the problem when I tried to destroy one of my VMs and was bombarded by UAC prompts.
The text was updated successfully, but these errors were encountered: