Update guest additions in downloadable Vagrant box

[techtonik]

Vagrant VM occasionally hangs and or makes some files inaccessible. vagrant up warns that this is likely to be caused by outdated guest additions. It would be nice to see base box updated.

==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 4.3

Here are some links:
https://github.com/TryGhost/Ghost-Vagrant#updating-virtual-box-guest-additions
http://stackoverflow.com/questions/20308794/how-to-upgrade-to-virtualbox-guest-additions-4-3-on-precise64-box

[techtonik]

Manual way for updating additions for Ubuntu 12.04 on VirtualBox:

• bring box to initial state

vagrant destroy
vagrant up --no-provision
vagrant halt

• start it through VirtualBox and mount CD image
• vagrant ssh
• mount cd, upgrade kernel (to fetch newer sources), update additions

sudo mount /dev/sr0 /media/cdrom
cd /media/cdrom
sudo apt-get update
sudo apt-get upgrade
# hmm, it upgrades everything but kernel with headers =/

[techtonik]

Figured out that I need to use apt-get dist-upgrade to upgrade kernel and headers. But that's all I could handle for now. It looks like it might be better to recreate the box from scratch with Ubuntu 14.10. @whit537, what is the OS that is running in production?

[chadwhitacre]

$ heroku run "lsb_release -a"
Running `lsb_release -a` attached to terminal... up, run.1291
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 20, in <module>
    from optparse import OptionParser
ImportError: No module named optparse
$

😞

[chadwhitacre]

We're on 10.04:

$ heroku stack
=== gratipay Available Stacks
  bamboo-mri-1.9.2
  bamboo-ree-1.8.7
  cedar-14 (beta)
* cedar

$

[techtonik]

It is possible to switch to cedar-14.

I updated the box with additions successfully, but it is now 880Mb. So it may worth just to redo it from scratch using more fresh 14.04 image and clean it afterwards. We can test if Gratipay behaves correctly on 14.04 then.

[chadwhitacre]

It is possible to switch to cedar-14.

I'm sure it's possible, not sure it's worth it. I would say go ahead and use Ubuntu 14.04 in the Vagrant box. We're already out of sync with production since Vagrant currently uses 12.04 (right?). And I develop on Mac OS anyway, so we haven't tried too hard to keep dev and production OSes in sync.

[techtonik]

Closed by #2954. New base image used by Vagrantfile already has new VirtualBox additions installed. Just need to make snapshot of the box and pack it properly.

[AnsonHwang86]

perfect ,remark