GitHub user johnmccabe opened a pull request:
https://github.com/apache/brooklyn-dist/pull/86
switch vagrant boxes to bento images
Prior to this PR running the vagrant getting started environment would fall
back to using rsync for making the /vagrant share available in the guest OS due
to the `centos/7` box not including virtualbox guest
additions (resulting in the absense of the vboxfs drivers). This would
complicate using the vagrant env on Windows where rsync is not available by
default. The `centos/X` boxes do not following current best practices for
virtualbox providers.
This commit switches to the community managed bentos centos-7.3 box which
follows best practices and includes the vbox guest additions. See -
https://github.com/chef/bento
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/johnmccabe/brooklyn-dist
maint/master/switch-to-bento-box
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-dist/pull/86.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #86
----
commit 01d162da021dd7c3438ed99294c977917c24929f
Author: John McCabe <[email protected]>
Date: 2017-02-25T09:15:14Z
switch vagrant boxes to bento images
Prior to this commit running the vagrant getting started environment
would fall back to using rsync for making the /vagrant share available
in the guest OS due to the `centos/7` box not including virtualbox guest
additions (resulting in the absense of the vboxfs drivers). The
`centos/X` boxes do not following current best practices for virtualbox
providers.
This commit switches to the community managed bentos centos-7.3 box
which follows best practices and includes the vbox guest additions. See
- https://github.com/chef/bento
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
