(In the dialog below, italics represents the thought process and feedback of one of our senior Linux Engineers) Sometimes we answer random ‘What do you recommend?’ questions, and other times quick off the wall ‘Stumpers’ for their dev team. It’s a good example of what we can bring to the table for ongoing support and escalations as a valuable resource to them. This client is US based company with internal software development and operations team. Thanks everyone, this one has been fun! Ha.Here is an example of a High Level Help Desk interaction with a client. It could also be interesting to start taking pieces out of Vagrantfile and provision.sh to see if we can identify exactly where the problem is caused. Can we move this to a new ticket? My next recommendation is a complete uninstall of Vagrant and Virtualbox. I'm going to close this out as I believe the original issue has been resolved via I'm still confused by your issue and I think it's a separate one. This is a feature for convenience rather than a requirement. If vagrant-hostsupdater is not installed, then no su access is required. If we can also document some creative OS specific processes in the VVV wiki that can be taken to avoid entering the password, that would be great as Correct. And in step 8 to highlight the possible need to enter a password to continue. In step 4 to clarify that vagrant-hostsupdater is recommended, not required, with a note about possible password requirements. I think there's room for some additional docs in the README. It looks like the only thing we do now is mention it in Vagrantfile here So after spending 37 minutes provisioning, setting up the hosts file, it then very helpfully shuts down and destroys the I agree, documentation can definitely be improved around this. Running cleanup tasks for 'shell' provisioner. Reply to this email directly or view it on GitHub.Įxternal network connection established, packages up to date. Is there any way you can capture the output of an entire vagrant up after a vagrant destroy and paste the output into a gist? Reaching for straws now that has a Mac, but he may have some input on issues with Windows 7 as well. :) I'm almost wondering if there's some kind of permissions issue with your Windows 7 setup. If starting from scratch via destroy, there is no problem at I'm feeling stumped, hence the no reply. Until we get #148 worked out, I've resorted to always using vagrant provision when I want to apply provisioning after an up or a halt and only using vagrant up to power on the machine. To issue, I feel like I saw that the other day on my machine that's running Virtualbox 4.2.18, but not the one that is running Virtualbox 4.2.3. On Oct 29, 2013, at 12:07 AM, Jeremy Felt wrote: Some further notes: I'm finding this happens quite frequently and I need to provision after most reboots (if not all).Īs a side note, I had originally tried virtual box 4.2.3 and had the exact same issue, re-read the documentation and thought I should downgrade.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |