I've been following the discussion about several Xenial Vagrantbox issues closely, because we're affected by them.
Vagrantboxes are frequently updated and take a notoriously large amount of time to download. If including config management tools doubles the size of the image, and it doesn't even include the config management tool *we* use (Ansible), then there's no benefit in our specific situation.
I agree that a major release is a good moment to introduce breaking changes, and I humbly believe having the cloud images and Vagrantbox align is a stronger point than what used to be in previous releases.
For reference, current VirtualBox Vagrantboxes from various vendors:
- debian/jessie64 is 280mb (no tools)
- ubuntu/trusty64 is 423mb (includes tools)
- ubuntu/xenial64 is 279mb (no tools)
- centos/7 is 483mb (no tools)
- fedora/24-cloud-base is 210mb (no tools)
I've been following the discussion about several Xenial Vagrantbox issues closely, because we're affected by them.
Vagrantboxes are frequently updated and take a notoriously large amount of time to download. If including config management tools doubles the size of the image, and it doesn't even include the config management tool *we* use (Ansible), then there's no benefit in our specific situation.
I agree that a major release is a good moment to introduce breaking changes, and I humbly believe having the cloud images and Vagrantbox align is a stronger point than what used to be in previous releases.
For reference, current VirtualBox Vagrantboxes from various vendors:
- debian/jessie64 is 280mb (no tools) 24-cloud- base is 210mb (no tools)
- ubuntu/trusty64 is 423mb (includes tools)
- ubuntu/xenial64 is 279mb (no tools)
- centos/7 is 483mb (no tools)
- fedora/