On Wednesday, June 11, 2014 11:41:09 AM UTC+2, Alvaro Miranda Aguilera 
wrote:
>
> I am assuming you are on OSX, so apologies if I am incorrect.
>
 hi Alvaro, yes I'm on osx. sorry for not being explicit about that.

>
> If that's the case, I believe the default setup will create a virtualbox 
> machine and run the containers there, so you have 3 options here.
>
> 1. Open virtualbox gui and stop/delete the vms that are left orphan
>
they are no more visible. 
I do not remember exactly what I did to let them orphan/zombie, probably I 
forgot to stop them before deleting the corresponding folder.   

> 2. ps aux | grep -i virtualbox, and kill those proceeses.. then check 
> ~/Virtualbox VMs folder
>
as above. I can only see them, even after a reboot, with the vagrant 
global-status command.

> 3. reboot, and check the vms folder.
>
Perhaps I can try to completely unintall docker and vagrant. Do you no if 
there is any unistall trick for them?

Thanks so much
mimmo
 
On Wed, Jun 11, 2014 at 4:16 AM, Giacomo Cosenza <[email protected] 
<javascript:>> wrote:

> Hi there, I'm pretty new to vagrant/docker. While palying around I 
>> discovered that I did not halt/destroy a docker and a vagrant vm before 
>> deleting their corresponding folder. Running the vagrant global-status from 
>> any directory I get the following result:
>>
>> $ vagrant global-status
>> id       name    provider   state   directory
>> ------------------------------------------------------------------------
>> d4fcaec  default virtualbox running /Users/mimmo/Developer/docker
>> cd85a7a  default virtualbox running /Users/mimmo/vagrant
>>
>> The above shows information about all known Vagrant environments
>> on this machine. This data is cached and may not be completely
>> up-to-date. To interact with any of the machines, you can go to
>> that directory and run Vagrant, or you can use the ID directly
>> with Vagrant commands from any directory. For example:
>> "vagrant destroy 1a2b3c4d"
>>
>> both the above ../Developer/docker and vagrant directories do not exist 
>> any more and even if I reboot the system they are still there.
>>
>> Is there a way to kill them?
>>
>> Thanks
>>
>> mimmo
>>
>>  -- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to