On 06/02/2016 11:08 AM, Andrew Lee Rubinger wrote: > Thanks for sending this along. > > Because I'm newer to Vagrant; does "vagrant destroy" sufficiently clean up so > that the next "up" operation is a clean state? Or in libvirt does this have > the same issue as you mention with caching in the storage pool? >
The 'vagrant destroy/vagrant up' works completely fine. The existing box will be removed and the new box will be clean. The problem I am refering to is when you trying to "update" the underlying base image (i.e. a new version of the CDK comes out). In this case if you don't properly remove the old CDK box from libvirt before adding the new box, then you'll most likely be using the wrong bits. _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
