Machine is destroyed during provisioning

[Franz Liedke]

I am having some trouble with my shell provisioning scripts (using Vaprobash) on Windows.

Provisioning seemed to work well at first, but then it failed during the installation of phantomjs (via sudo apt-get). It didn't just fail, though, it simply went on to destroy my VM completely (and repeatedly).

I restructured my provisioning scripts a little bit, and now the same happens during the installation of global NPM packages.

Is this supposed to happen? What can cause Vagrant to destroy machine during provisioning?

[Alvaro Miranda Aguilera]

What do you mean on windows?

Windows host, linux guest?

Can you share a zip of your project?

Also, check your issue/error is not on a issue on that project:
https://github.com/fideloper/Vaprobash/issues

Alvaro

> --
> 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 vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Franz Liedke]

Yes, Windows host, linux guest.

The project is available on GitHub: https://github.com/flarum/flarum

I just updated Vagrant (I was running v1.5.1), and now it's not being destroyed, but instead the provisioning script fails with a segmentation fault. That I can hopefully fix... =)

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/eMDoldUmsWI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.