Skip to content
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.

artifacts? #297

Open
jloomb opened this issue Jan 30, 2016 · 1 comment
Open

artifacts? #297

jloomb opened this issue Jan 30, 2016 · 1 comment

Comments

@jloomb
Copy link

jloomb commented Jan 30, 2016

Am I meant to get a new unique 'berkshelf' in .berkshelf/vagrant-berkshelf/shelves/ ever time I vagrant up that remains after I vagrant destroy. Is there any options to prevent this as creating duplicate after duplicate whilst I'm developing means I need to manually watch/maintain the ever growing shelves folder?

@reset
Copy link
Contributor

reset commented Feb 1, 2016

@jloomb yep, each virtual machine you begin to manage needs to have it's own self contained shelf. The contents of the shelf should be rather small and it should be cleaned up on destruction. If the shelves aren't being cleaned up then there may be some places where we aren't correctly cleaning up after ourselves

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants