--
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/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4bf28297-827e-42e6-9b16-bcccf08a61cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
hellohow do you reboot the box?how to reproduce this? if you can share a detailed set of instructions to reproduce this, i think will be easier to understand.thanks
On Tue, May 9, 2017 at 6:08 PM, Robert Lee <ggl...@gmail.com> wrote:
Without fail, anytime I'm SSH'd into my box and my host machine restarts, I'm stuck with a corrupt file.
When I attempt to either restore an old save or just revert to a prior snapshot, Vagrant decides to provision a new box, which is effectively forcing me to rebuild the box every time.Is this expected behavior?
--
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/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4bf28297-827e-42e6-9b16-bcccf08a61cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Alvaro