in those links talk about 1G of ram how much does your guest have?
On Tue, May 20, 2014 at 2:42 AM, Chris Fidao <[email protected]> wrote: > I've never run into errors of running out of memory during provisioning > until I updated to Vagrant 1.5+. This coincides with also use Ubuntu's > 14.04 image on vagrantcloud.com. > > Specifically, installing certain things exhausts memory limits and causes > provisioning to fail. HHVM + composer and HHVM+ some composer packages is > one example. Installing things like mailcatcher is another. > > All of these provisioning scripts are bash scripts, as seen on my > Vaprobash <https://github.com/fideloper/Vaprobash> project. > > Most of these installs work just find post-provisioning, if done manually. > I'm wondering if Vagrant doesn't allow for more memory usage than the > "base" amount specified during provisioning? > > I'm not sure where to look to start debugging these issues - I'd rather > not have to default memory allocated to a higher than necessary, nor force > users to have to learn about and decide to give more RAM to their VM's in > context of Vaprobash. > > Examples: > > - https://github.com/fideloper/Vaprobash/issues/336 > - https://github.com/fideloper/Vaprobash/issues/313 > - https://github.com/fideloper/Vaprobash/issues/333 > > > Any suggestions (or clarification questions) appreciated! > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
