Closed bitliner closed 7 years ago
Hi. There isn't much here to be able to reproduce this error. I had a few runs using the virtualbox provider and was unable to reproduce. If you can provide a simple Vagrantfile that can reliably reproduce the error you are encountering, please open up a new issue. Thanks!
@chrisroberts - I have a similar issue.
Vagrant 1.9.0 - on WIndows 10. Running Homestead box v1.0.1 "wmware" - This is running Ubuntu 16.04 (same as above)
We've confirmed it affects other users running Windows 10 and this box - i,e. it is not just me. This SO question summizes the issue perfectly: http://stackoverflow.com/q/33393077/1317935 . I dropped a 500 bounty on the question to try to get a solution - but nothing yet.
Note: it talks about not being able to clone - but I also see the regularly git commit
error above, so I think it is likely the same issue
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Vagrant version
Vagrant 1.8.6
Host operating system
Mac OS Sierra
Guest operating system
puppetlabs/ubuntu-16.04-64-puppet
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we may be unable to assist with your issue. Try to reproduce the issue using a vanilla Vagrantfile first.
Debug output
Provide a link to a GitHub Gist containing the complete debug output: https://www.vagrantup.com/docs/other/debugging.html. The debug output should be very long. Do NOT paste the debug output in the issue, just paste the link to the Gist.
Expected behavior
git working fine
Actual behavior
Quite often, if I run git commit the result is
Sometimes, when I run
git add
, the result is