Re: [vagrant-up] vagrant box repackage

[Alvaro Miranda Aguilera]

hello

you need to destroy and up so the new VM gets created from the new template.

if you share the fulll sequence of steps, that will help to confirm you have all the steps or maybe one is missed.

alvaro

On Wed, Oct 3, 2018 at 2:21 PM anonymous X <nicol...@gmail.com> wrote:

What's the point of this subcommand when it doesn't save the current state of the VM.

I installed new packages on my VM box. Then I repackaged it. Removed the old, added the repackaged to my VM and did vagrant up. The repacked VM didn't have all things that I had installed.

--
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/ce830327-8fe0-42b1-bbb2-4645f5318d2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro