-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vagrant-lxc and stack to deep #70
Comments
Seems to be not |
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 :) |
New vagrant version should be released today or early next week with the fix, along with other improvements on the 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 ! |
Fixed in latest |
We have a workaround to set the provisionner to
ansible
when the lxc provider is used in order to avoid fgrehm/vagrant-lxc#398However 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
The text was updated successfully, but these errors were encountered: