You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
@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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: