Hi, Thanks for the suggestions, unfortunately neither worked. At least I have a workaround using the 'vagrant ssh' command to set the locale before running the provision script.
It would be nice to get it working on a 'vagrant up' with simple provisioning scripts (or at least to understand why it doesn't work the way I expect). Thanks, Rich. On Monday, July 6, 2015 at 11:37:42 PM UTC+1, Alvaro Miranda Aguilera wrote: > > On Tue, Jul 7, 2015 at 4:35 AM, Richard Murray <[email protected] > <javascript:>> wrote: > > config.vm.provision "shell", path: "provision_locale.sh" > > config.vm.provision "shell", path: "provision.sh" > > > hello, this is probably how the shells are created (local shell, subshell, > etc) > > try this: > > config.vm.provision "shell", inline: "source /vagrant/provision_locale.sh" > config.vm.provision "shell", inline: "bash /vagrant/provision.sh" > > The first one, using source should set the values for current shell > the second one should create a sub shell, that may inherit the values > of the first > > if doesn't work, you can test: > > config.vm.provision "shell", inline: "source /vagrant/provision_locale.sh" > config.vm.provision "shell", inline: "source /vagrant/provision.sh" > > > > 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/18cd3264-abe8-45b4-ae8d-ed770043e490%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
