I got to the bottom of it... It was because the script was being stored on git and checked out on a windows machine. On my linux host, this caused no problems, but on their windows machine git was converting line endings.
Because this was a script called within a script, vagrant wasn't automatically converting line endings, so I had to pass the script through dos2unix before running it on the windows host. Not sure if there's a better way, but this hack got things working for now... Marcus On Thursday, 29 March 2018 10:31:39 UTC+1, Alvaro Miranda Aguilera wrote: > > Hello > > worth to check they have a copy of all the files. > > > not sure the internals, but basically on this other person VM, this file: > /var/www/bin/run_es_vagrant.sh > > doesnt exists. > > Not sure how those files get there, but maybe a failed provisioning. > > alvaro > > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/b1f461f2-2042-42ad-9702-75f5320a7706%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
