vagrant-lxc and stack to deep

[krtek4]

We have a workaround to set the provisionner to ansible when the lxc provider is used in order to avoid fgrehm/vagrant-lxc#398

However this does not work if the provider is not set explicitly and sadly on Linux the LXC provider is chosen by default after the Vagrantfile is ran, so there's also no way to know it will be used before it's too late :(

We should at least document that.

References

• https://www.vagrantup.com/docs/providers/basic_usage.html section "Default Provider"
• Get current provider in Vagrantfile hashicorp/vagrant#1867
• https://groups.google.com/forum/#!topic/vagrant-up/XIxGdm78s4I

[krtek4]

Seems to be not lxc related : hashicorp/vagrant#6984

[krtek4]

There's been some movements on hashicorp/vagrant#6984

A fix was just pushed to vagrant. So we can expect this to be resolved in the next Vagrant version :)

[krtek4]

New vagrant version should be released today or early next week with the fix, along with other improvements on the ansible_local front ( hashicorp/vagrant@bb9dba5#commitcomment-17800415 )

Will do some cleanup just afterwards and bump the required version to 1.8.2 in the Vagrantfile as soon as I have time to do some testing !

[krtek4]

Fixed in latest Vagrant version. The hacky code was cleaned by Chregu.