I would suggest keeping the root volume as minimal as possible for the
box and then let the end users to grow it using methods provided by
Vagrant.  Anyone then can grow the volume to their specific use case,
its a lot easier than reducing a default, large disk provided with a
box.

Cheers,
Tim

On 8 July 2015 at 19:31, Lalatendu Mohanty <lmohanty@redhat.com> wrote:
> On 07/08/2015 10:32 PM, Jeff Sheltren wrote:
>>
>> Hi, I've started doing some testing on the Virtualbox Vagrant box
>> (http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-1505-x86_64-01.box)
>>
>> I've hit a couple of issues:
>>
>> 1) The disk size, at about 8 GB, is too small.  Could it be bumped to
>> 50-100 GB? Since the on-disk image will grow dynamically this won't take up
>> that much space by default but will make it usable for those that need more
>> storage on the root partition (and I don't want to have to custom mount
>> additional partitions).
>>
>
> Yes, this can be fixed. I am fine with bumping the disk size to 50GB as it
> would be sparse disk. Also there are few tricks you can do with the
> Vagrantfile to increase the disk size. But I have not tried them
>
>> 2) The VirtualBox Guest Additions aren't included.  I'm assuming this is
>> due to a licensing issue and not that they were simply not considered but
>> wanted to double check.
>>
>
> This part I am not sure. I need to check how we can add "VirtualBox Guest
> Additions". yes, we want to fix this.
>>
>> Otherwise it's been great, and saves me having to build my own custom box,
>> which is definitely a win.
>>
>> -Jeff
>
>
> How do we track these issues? I just dont want to loose track of these.
>
> -Lala
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel@centos.org
> http://lists.centos.org/mailman/listinfo/centos-devel
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel