[CentOS-devel] Disk size on Vagrant image

Jeff Sheltren jeff at tag1consulting.com
Tue Sep 12 21:01:26 UTC 2017

On Tue, Sep 12, 2017 at 2:42 PM, Laurentiu Pancescu <
lpancescu at centosproject.org> wrote:

> On 12/09/17 20:51, Jeff Sheltren wrote:
>> Hi Laurentiu, have you had a chance to look at the xfs issue around
>> zerofree?
> I'm sometimes too tired to do much besides dropping to bed (I wake up at
> 6AM and only manage to arrive home between 20-21). I haven't finished the
> XFS documentation yet. :(

No problem, IMO the switch to ext4 makes more sense anyway, but let's see
what others think.

> Is it possible and worth creating a "7-minimal" vagrant image in addition
>> to the default one currently built? For my needs, minimal (with a larger
>> partition!) would be perfect because I just want a small, standard CentOS
>> image that can then be configured with whatever config management system
>> to
>> prep it for development.
> May I ask why creating your own image with my Packer script isn't an
> option?  It would closely follow our image (I merge the changes from the
> official images when necessary).  You could upload it to Vagrant Cloud to
> have available for the rest of your team and your customers.
That's possible -- and we've built our own custom boxes in the past -- but
it's additional work to build each time there's an upstream release. If I
were to go this route only to increase the disk image size, I'd consider
building a customized image per-client instead (with puppet pre-run), and
that's what I'm trying to get away from. For the most part we've been happy
with your Vagrant image, we're just hitting these disk size issues for some
clients with large data sets.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20170912/1dbdcdf9/attachment.html>

More information about the CentOS-devel mailing list