Hi Sorcerer Stone,
:) Happy to help. I actually don't usually poke around with those
files/folders in the "VirtualBox VM" folder (on the host).
So I'm not sure I understand if you're referring to files in that folder,
or if you're referring to folders inside the VM.
But, anyway, I don't know the answer to that one. If there is anything
worth saving within your VM, you should be saving it
in a shared folder. If a cache doesn't survive a reboot you can always
`vagrant reload` to restart the VM.
But, files inside the VM are all contained in a virtual disk file with name
[your VM name].VMDK {or VDI, RAW, other virtual disk formats} or similar.
Just look for the largest file (in "VirtualBox VM") and you'll find it.
I hope that helps,
Dennis
On Friday, 8 May 2020 16:48:51 UTC-4, Sorcerer Stone wrote:
>
> Hello Dennis,
> Thanks again (Ran into you again!!)
> Ok. I think I got this problem under control done. I foolishly did
> "vagrant destroy" to clean both projects.
> Then I looked into this ".vagrant.d" directory. Most of the sub-folders,
> in particularly "data" were empty. What ever remains in other subfolders
> were pre-dated to my problems. So, I ignored them.
> Then I "vagrant up" the first project (the one I kept all default settings
> of Vagrant). It ran.
> Then I "vagrant up" the second project. It generated the same error. But
> this time, there were new suggestions that I should look at a directory
> which I didn't know it exist. It is called "VirtualBox VMs". I poked inside
> this folder.
> It has, as you mentioned above, images of all my previous VMs for my
> projects.
> I deleted the image for the project in question. Then I ran "Vagrant Up"
> for it.
> The second project is up and I am able to ssh into the VM using the new
> ssh port forwarding settings.
> Thanks.
>
> BTW. Another newbie question.
> If I want to purge all the folders created by a particular VM (say, I
> corrupted the configurations and need to clean them out) - short of
> destroying the VM and rebuilding it again, is there some vagrant commands
> (on Host OS) I can use so that I can purge all the temporary cache data in
> the relevant directory within the VM in question? If there is, can you
> kindly point the URL so that I can read up?
>
>
>
> On Friday, May 8, 2020 at 1:52:43 PM UTC-4, Dennis Chang wrote:
>>
>> Hi Socerer Stone,
>>
>> So .vagrant directory exists within your folder (which also contains your
>> Vagrantfile).
>> However, the actual box exists on "C:\Users\yourname\.vagrant.d" and
>> `vagrant destroy` should delete it.
>>
>> My .vagrant.d
>>
>> ```
>> Windows2012R2 dchang$ ls -l ~/.vagrant.d/
>> boxes/ gems/ plugins.json
>> setup_version
>> data/ insecure_private_key rgloader/ tmp/
>> Windows2012R2 dchang$ ls -l ~/.vagrant.d/boxes/
>> alpine-3.10/
>> generic-VAGRANTSLASH-centos6/
>> alpine-VAGRANTSLASH-alpine64/
>> generic-VAGRANTSLASH-centos7/
>> bento-VAGRANTSLASH-ubuntu-14.04-i386/
>> mwrock-VAGRANTSLASH-Windows2012R2/
>> cb-training-certification-1584111440/
>> mwrock-VAGRANTSLASH-Windows2016/
>> cb-training-jenkins-fundamentals-1550622005/
>> ubuntu-VAGRANTSLASH-bionic64/
>> cb-training-pipeline-fundamentals-1574353126/ ubuntu-VAGRANTSLASH-focal64/
>> centos-VAGRANTSLASH-7/
>> ubuntu-VAGRANTSLASH-xenial64/
>> dchang-VAGRANTSLASH-centos7/
>> windows-2000-professional-base/
>> ```
>>
>>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/82a689fe-a81d-4391-8f88-015beef55490%40googlegroups.com.
