[vagrant-up] is it necessary to destroy a Vagrant box after updating it?

[William Arcaya C.]

Posts read:

https://superuser.com/questions/1164022/vagrant-box-update-vs-apt-get-upgrade

https://stackoverflow.com/questions/25914383/update-a-vagrant-box

According to these posts I need destroy my box with guest ArchLinux to take
effect the changes. I thought that a Vagrant box was like a virtual drive
but running under command line. I have a framework
ArchLinux-PHP-MariaDB-NGINX in that box, and I don't want to reinstall all
of them once again per every update for Vagrant box, so: is it necessary to
destroy a Vagrant box after updating it? Which are pros and cons if I don't
destroy it?

Thanks in advance.
--
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/1fb3e8fc-4115-4f81-9fa8-f216600d1618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

hello.

if you do changes to the Vagrantfile, you can use vagrant reload

if you do changes to the provisioners of the box, you can either use

vagrant provision
vagrant reload --provision


if you do changes to the base box, then yes, a destroy/up is needed.

if you are using local boxes, then destroy/up is whats needed.

if you are using boxes in vagrant cloud and a new version is up, then

vagrant box update
vagrant destroy
vagrant up

will be enough.


What changes and how you are doing them?

Alvaro

Post by William Arcaya C.
https://superuser.com/questions/1164022/vagrant-box-update-vs-apt-get-upgrade
https://stackoverflow.com/questions/25914383/update-a-vagrant-box
According to these posts I need destroy my box with guest ArchLinux to
take effect the changes. I thought that a Vagrant box was like a virtual
drive but running under command line. I have a framework
ArchLinux-PHP-MariaDB-NGINX in that box, and I don't want to reinstall all
of them once again per every update for Vagrant box, so: is it necessary to
destroy a Vagrant box after updating it? Which are pros and cons if I don't
destroy it?
Thanks in advance.
--
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
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/1fb3e8fc-4115-4f81-9fa8-f216600d1618%40googlegroups.com
<https://groups.google.com/d/msgid/vagrant-up/1fb3e8fc-4115-4f81-9fa8-f216600d1618%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro
--
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/CAHqq0ewKgLy0jdB_NLe3j_MUs%2B%3DfssBHqh%3DUJKHk1jV4iSYBoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[William Arcaya C.]

Thanks Alvaro,
But my question is: MUST I necessarily to destroy my box? Or is there a problem if I wanna keep it as is now? because I don't wish reinstall again my framework. Or is there a better solution?
Thanks in advance.


Sincerely,
                 William Arcaya C.《Beatus vir qui suffert tentationem,Quoniqm cum probates fuerit accipient                 coronam vitae》
《Sent from my Samsung tablet》

-------- Original message --------
From: Alvaro Miranda Aguilera <***@gmail.com>
Date: 09/10/2018 15:30 (GMT-05:00)
To: vagrant-***@googlegroups.com
Subject: Re: [vagrant-up] is it necessary to destroy a Vagrant box after updating it?

hello.
if you do changes to the Vagrantfile, you can use vagrant reload
if you do changes to the provisioners of the box, you can either use
vagrant provisionvagrant reload --provision

if you do changes to the base box, then yes, a destroy/up is needed.
if you are using local boxes, then destroy/up is whats needed.
if you are using boxes in vagrant cloud and a new version is up, then 
vagrant box updatevagrant destroyvagrant up
will be enough.

What changes and how you are doing them?
Alvaro
On Sat, Oct 6, 2018 at 7:26 PM William Arcaya C. <***@gmail.com> wrote:
Posts read:
https://superuser.com/questions/1164022/vagrant-box-update-vs-apt-get-upgrade
https://stackoverflow.com/questions/25914383/update-a-vagrant-box
According to these posts I need destroy my box with guest ArchLinux to take effect the changes. I thought that a Vagrant box was like a virtual drive but running under command line. I have a framework ArchLinux-PHP-MariaDB-NGINX in that box, and I don't want to reinstall all of them once again per every update for Vagrant box, so: is it necessary to destroy a Vagrant box after updating it? Which are pros and cons if I don't destroy it?
Thanks in advance.
--
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/1fb3e8fc-4115-4f81-9fa8-f216600d1618%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
Alvaro
--
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/CAHqq0ewKgLy0jdB_NLe3j_MUs%2B%3DfssBHqh%3DUJKHk1jV4iSYBoQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
--
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/ol317rcavs66u0vv1yk89w1v.1539118081447%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

if you don't destroy, the current box won't apply any change as was created
from a previous template.

alvaro
--
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/CAHqq0ewnzXOX1vZUj4YXfWsX%2Bn71m3DQrnOsGN-cG2rMM9cb8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.