hello vagrant uses his own ruby version.
if you want something older, you can check the changelog, and try an older version https://releases.hashicorp.com/vagrant/ https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md#201-november-2-2017 alvaro. On Mon, Apr 13, 2020 at 6:20 PM Frank Rehwinkel <frankrehwin...@gmail.com> wrote: > $ vagrant plugin install vagrant-aws >> Installing the 'vagrant-aws' plugin. This can take a few minutes... >> Vagrant failed to properly resolve required dependencies. These >> errors can commonly be caused by misconfigured plugin installations >> or transient network issues. The reported error is: >> ovirt-engine-sdk requires Ruby version >= 2.5. > > > Running on macOS with vagrant installed via homebrew. > > Since the vagrant-aws plugin worked for me last year, two things have > changed that I can tell. > > vagrant went from 2.2.5 to 2.2.7 and after seeing the plugin install step > failed, and checking through gems and GitHub, I see ovirt-engine-sdk has > gone from 4.3.0 to 4.4.0 a few days ago, while vagrant-aws hasn't changed > in well over a year. And the git log for ovirt-engine-sdk-ruby does seem to > indicate a version in their config went from 2.4 to 2.5 but I can't attest > that is a ruby version. > > I've looked at the vagrant-aws gem and it doesn't rely on ovirt-engine-sdk > directly but it pulls in fog and iniparse and a few other things. I also > haven't seen how to specify an older version of a plugin or an older > version of a dependency of a plugin. > > I did find how to use homebrew to pull in an older vagrant, but dropping > back to 2.2.5 didn't make any difference. The 4.4.0 version of > ovirt-engine-sdk was still a failing dependency. > > Homebrew has my ruby version at 2.7.1 but I've ready vagrant comes with > its own ruby although I don't see it in the homebrew Casks directory. > > Should I be looking at why vagrant doesn't have access to my 2.7.1 ruby or > how to get back to 4.3.0 of ovirt-engine-sdk or perhaps why > ovirt-engine-sdk is even needed in my setup? I want to use vagrant to start > up an aws machine and give me ssh access to it. > > Thanks. > > -- > 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 vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/d30e9936-81c0-4854-b0a7-38e361c5366d%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/d30e9936-81c0-4854-b0a7-38e361c5366d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ex%2BN_OU5SPka2%3D5912F3TgsotxYYkKQLRsUp9grF3qejA%40mail.gmail.com.
