Hi Dusty,
On 2/12/20 4:43 PM, Dusty Mabe wrote:
This is mostly because the cloud images don't configure any swap and we keep our
image builds for the vagrant boxes and for the cloud images pretty much the same.
Thanks for your quick answer. This makes sense.
Would you have a pointer on which scripts/stack are generating the base
boxes? One way I see would be to remake the base boxes here.
There are two pretty easy options:
- increase the amount of ram for the vagrant box
Yes, this is my current solution, I am doing that in the Vagrantfile.
- configure a second disk in your vagrantfile and then set it up for swap
Do you have a pointer on how to do that? AFAIS[1] the Vagrant disk
feature is still experimental and not fully documented.
I am using the VirtualBox provider so maybe you were referring to using
the VBoxManage configuration hook[2] or remaking the base box itself[3]
(hence my question above about how the Fedora base boxes are made)?
Thanks again for your help here!
Vincent
[1] https://www.vagrantup.com/docs/disks/usage.html
[2]
https://www.vagrantup.com/docs/virtualbox/configuration.html#vboxmanage-customizations
[3] https://www.vagrantup.com/docs/virtualbox/boxes.html#virtual-machine
--
www.iot.bzh
_______________________________________________
cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/cloud@xxxxxxxxxxxxxxxxxxxxxxx
