-
Notifications
You must be signed in to change notification settings - Fork 665
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
Add parameter for vagrant provider override #1235
Conversation
See the docs for additional info on this option: https://www.vagrantup.com/docs/providers/configuration.html#overriding-configuration
2ded2b4
to
4bbb580
Compare
Made a PR upstream at ansible/molecule#1235. This was needed in order to disable nfs completely under libvirt for some reason.
@msheiny can you provide more information, specifically usage of your new option. |
Made a PR upstream at ansible/molecule#1235. This was needed in order to disable nfs completely under libvirt for some reason.
sureeeeeeeee @retr0h i'm specifically using it in this scenario:
I'm trying to disable synced folder mapping and NFS for the underlying box. No matter where else I try to put the NFS value I was unable to stop vagrant from bombing out without sticking it under the |
Thanks @msheiny can you add this example to https://github.com/metacloud/molecule/blob/master/doc/source/configuration.rst#molecule-vagrant-module ? I'll release 2.13 once your PR is complete. |
I'll do this. |
Will this disable folder syncing, if adding to platforms section?
|
Made a PR upstream at ansible/molecule#1235. This was needed in order to disable nfs completely under libvirt for some reason.
Made a PR upstream at ansible/molecule#1235. This was needed in order to disable nfs completely under libvirt for some reason.
Made a PR upstream at ansible/molecule#1235. This was needed in order to disable nfs completely under libvirt for some reason.
Our unique changes that were added to support suppressing NFS were recently merged upstream in molecule 2.13: * ansible/molecule#1235 * ansible/molecule#1233
Our unique changes that were added to support suppressing NFS were recently merged upstream in molecule 2.13: * ansible/molecule#1235 * ansible/molecule#1233
See the docs for additional info on this option:
https://www.vagrantup.com/docs/providers/configuration.html#overriding-configuration
While trying to disable nfs explicitly on a box that had it enabled... doing an over-ride on the provider was the only way I could get it working 🤷♂️ This might be a libvirt specific problem but adding this option fixed it for me and its optional.