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
I am new to Vagrant, which I am using to test Chocolatey packages I am developing. I am using the Vagrant Chocolatey Test Environment, which is working well.
Here are my naïve questions:
Does a vagrant sandbox commit survive the various Vagrant teardown commands, such as vagrant suspend and vagrant halt, and vagrant destroy? That is, will a vagrant up after that restore the VM state at the time the vagrant sandbox commit was issued?
Assuming that vagrant sandbox commit only survives a suspend, to establish a new suspend-surviving VM can I just issue:
vagrant sandbox on
do stuff on the vm
vagrant sandbox commit
vagrant suspend
The issue I'm dealing with is that the Chocolatey Test Environment (CTE) VM contains some software, such as Notepad++, that I am actually building packages for, so I don't want it to be installed on the VM when I start my package testing. I also don't want to have to uninstall all this software when I start my testing after working on other things for a while. Can you suggest the best practice workflow for this situation?
Thanks so much.
The text was updated successfully, but these errors were encountered:
I am new to Vagrant, which I am using to test Chocolatey packages I am developing. I am using the Vagrant Chocolatey Test Environment, which is working well.
Here are my naïve questions:
vagrant sandbox commit
survive the various Vagrant teardown commands, such asvagrant suspend
andvagrant halt
, andvagrant destroy
? That is, will avagrant up
after that restore the VM state at the time thevagrant sandbox commit
was issued?vagrant sandbox commit
only survives a suspend, to establish a new suspend-surviving VM can I just issue:The issue I'm dealing with is that the Chocolatey Test Environment (CTE) VM contains some software, such as Notepad++, that I am actually building packages for, so I don't want it to be installed on the VM when I start my package testing. I also don't want to have to uninstall all this software when I start my testing after working on other things for a while. Can you suggest the best practice workflow for this situation?
Thanks so much.
The text was updated successfully, but these errors were encountered: