-
Notifications
You must be signed in to change notification settings - Fork 189
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 vagrant architecture support #491
Conversation
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Not sure what is going on with that last failing spec test. |
Without really digging into things too much here it looks like winrm is failing, but the winrm support we have here is 9 years old and probably not necessary anymore. Vagrant natively supports that. I'm not sure we need the plugin anymore. That should probably all get refactored away and a major version bump of this cut. |
Signed-off-by: Tim Smith <[email protected]>
….0 since Oct 2018 Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Signed-off-by: Corey Hemminger <[email protected]>
Tested this as working. Test setup M3 macbook pro kitchen file without box_arch specified:
Same machine specifying
|
@tas50 would you be able to cut a new major release of this driver? |
I was planning to do a new one when I get into my office this morning |
cool thanks |
Description
added vagrant cpu architecture support when specifying boxes and providers
https://developer.hashicorp.com/vagrant/vagrant-cloud/boxes/architecture
https://app.vagrantup.com/bento/boxes/ubuntu-23.10
When not specified Vagrant defaults to the system CPU architecture for box downloads
Check List