Vvv: Upgrade ubuntu to 16.04 LTS

[halvardos]

Hi,

Thank you for creating VVV, it has saved me tremendous amounts of work!

Is there a reason why upgrading the base image for ubuntu to 16.04 has not been discussed?
Would it make the upgrading of other packages easier to maintain to bump the core system version?

[LoreleiAurora]

I would love this to happen but the official Ubuntu Xenial box is broken.
Therefore we must wait for the below tickets to be closed.

• vagrant vb ubuntu/xenial64 cannot mount synced folders
• Xenial vagrant image is missing its hostname in /etc/hosts

[halvardos]

aaah, that makes sense.

Thank you for the quick answer.
I started using the provisioning files from this project as a base for a docker container to get in line with the rest of our organisation but still keep my development environment the same.

And they use a more recent distro as base, so thats why I'm asking :)

If anyone else is interested i could share my docker implementation, it has some limitations atm. but generally works the same.

[ivankruchkoff]

Both issues have a confirmed fix in place.

[LoreleiAurora]

As the issues were changed from Fix Commited to Fix released on 2016-09-06 and was included in box release 20160907 i will start working on this at the weekend.

[LoreleiAurora]

There is yet another bug to get in our way 😢
xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf
The fix is committed but not yet in release.

[jeremyfelt]

Chatted with @LoreleiAurora a bit about this today. Let's keep an eye on the Xenial image over the next 6 months. Trusty is doing fine with the configuration that we have, and moving to a new box will definitely be a breaking change, so let's be sure it's working well with VirtualBox, VMWare Fusion, Parallels, etc.. before upgrading.

[wturrell]

It is possible to update your existing box manually if you want/need 16.04 right now.

Briefly, the approach I took was:

• take a snapshot for backup
• upgrade Ubuntu using do-release-upgrade
• machine then hung on reboot, eventually figured out the Grub fix I needed
• needed to upgrade one or two things e.g. mysql client/server. I was already using the ondrej-php packages to get PHP 7.1. Also took opportunity to clear out packages I no longer needed. Didn't need to reconfigure any sites, the shared directories etc.

P.S. handy thing to know if you ever need recovery console etc - the root password of the VM is vagrant

[half2me]

Any update on this?

[DArcMattr]

I have a WIP fork for a base box upgrade to Ubuntu 16.04. The official Ubuntu box is not acceptable in its current form, as it doesn't have a default 'vagrant' user, so I had to go with an alternative.

I changed external apt sources where appropriate, and the box comes up with some wonkiness: the first vagrant up appeared to stall on the Grunt-CLI installation step, and rvm produced some errors; it finished in time, and a second go at running the provision steps on the box I already had ran without a snag. I'm not sure if it's due to network issues, or something else I haven't accounted for.

https://github.com/DArcMattr/VVV/tree/current_lts

[smcjones]

As far as I can tell, Ubuntu seems incredibly resistant to ever producing something that will be vagrant ready because it doesn't match Ubuntu's self-imposed standardization requirements.

At some point before 14.04 EOL, VVV will hopefully make an upgrade. Ideally it would be to the official box, but bento/ubuntu16.04 is a user-driven and very stable build. I use it in other vagrant boxes I have and it works well.

https://app.vagrantup.com/bento/boxes/ubuntu-16.04

[dingo-d]

I tried upgrading to 16.04.3 LTS with do-release-upgrade within the vagrant ssh, and it broke the vagrant. So you should probably add some kind of warning not to do that :D

On the bright side I reordered my folders nicely this time, so at least there is something gained xD

[tomjn]

I expect upgrading would involve changing the Ubuntu box referenced in the Vagrant file to an Ubuntu 16 box, then destroying the VM and reprovisioning after taking a database backup

[dingo-d]

I had the backup of the databases and config files, and all the client work is on repositories, so nothing lost ;)

As for upgrading, I didn't think of changing the ubuntu in Vagrantfile (tbh not sure what to change it from ubuntu/trusty64 to ... ?).

[tomjn]

a quick google search suggests ubuntu/xenial64, no guarantees you won't run into issues though

[tomjn]

https://app.vagrantup.com/ubuntu/boxes/xenial64

[DArcMattr]

Ubuntu consistently produces vagrant boxes that are not ready to use in a vagrant environment. Other users have had to step forward to pack their own boxes for general use.

And where we are, 2 months away from the next scheduled LTS release, and the VVV project has not yet updated to the current one. I get that project stability is important, but also being able to use the most recent set of tools available, something an ancient LTS distro has to be finagled into supporting.

[tomjn]

@DArcMattr if it was that simple VVV would have updated a long time ago.

E.g. I could go and change the box needed today.. then have a lot of people complaining about lost MySQL databases tomorrow

If you can provide a way to update the base box automatically without destroying existing users setups let us know. Or if you know a way to do it but only for new users so it happens automatically when vagrant destroy;vagrant up --provision happens that also works

[DArcMattr]

The last time there was a transition to new LTS versions, a destroy & re-provision were necessary, but back then, the MySQL DB file was stored outside the vagrant box.

[tomjn]

Do you know if it's possible to check the current box used in the vagrant file?

[tomjn]

1469 should make this ticket obsolete by pre-building VVV boxes, VVV updates would be:

git pull
vagrant box update

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.