[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#989462: Vagrant box for large builds



Hi all
I am following the https://salsa.debian.org/cloud-team/debian-vagrant-images/-/merge_requests/11
and wanted to remark something that did not come to my mind earlier.

If the build you're using inside the Vagrant box needed need so much room in the filsystem, what about doing this build inside the /vagrant synced directory which is shared with the host ? (https://www.vagrantup.com/docs/synced-folders)

THis way you're only limited by the disk space of the host.
When using NFS, and providing you don't do fsyncs write (I doubt the builds tools are doing fsync) you get nearly host system performance.
I just verified that with fio.

When doing a mount over NFS you need root permission at the initial creation of the box to create the NFS export to the guest in /etc/exports.

vagrant will create and manage an entry like this:
# VAGRANT-BEGIN: 1000 9a45b17b-a2b0-4d05-852d-8e5cf1709068
"/home/manu/Projects/vagrenvs/kuberdebian" 192.168.121.91(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,fsid=4201683301)
# VAGRANT-END: 1000 9a45b17b-a2b0-4d05-852d-8e5cf1709068


but you only need this root permission *at box creation* and not for further start/stop.

What do you think ? Any reason not to use the shared /vagrant directory for your builds ?


Reply to: