I think this a non-issue. Only problem was my assumption on the plugin
provider installation mechanism.
After installing VirturalBox using my host platform software installer
(dnf in my case) the command to start the VM succeeded.
$ sudo dnf install VirtualBox
.....
.....
Installed:
VirtualBox-6.0.14-1.fc30.x86_64
akmods-0.5.6-20.fc30.noarch
elfutils-libelf-devel-0.177-1.fc30.x86_64
kmodtool-1-34.fc30.noarch
akmod-VirtualBox-6.0.14-1.fc30.x86_64
VirtualBox-kmodsrc-6.0.14-1.fc30.noarch
VirtualBox-server-6.0.14-1.fc30.x86_64
Complete!
$ vagrant up
Bringing machine 'testinventory1' up with 'virtualbox' provider...
==> testinventory1: Importing base box 'geerlingguy/ubuntu1404'...
==> testinventory1: Matching MAC address for NAT networking...
==> testinventory1: Checking if box 'geerlingguy/ubuntu1404' version
'1.2.12' is up to date...
==> testinventory1: Setting the name of the VM:
tmp_testinventory1_1571664664932_17595
==> testinventory1: Clearing any previously set network interfaces...
==> testinventory1: Preparing network interfaces based on configuration...
testinventory1: Adapter 1: nat
testinventory1: Adapter 2: hostonly
==> testinventory1: Forwarding ports...
testinventory1: 22 (guest) => 2222 (host) (adapter 1)
==> testinventory1: Running 'pre-boot' VM customizations...
==> testinventory1: Booting VM...
==> testinventory1: Waiting for machine to boot. This may take a few
minutes...
testinventory1: SSH address: 127.0.0.1:2222
testinventory1: SSH username: vagrant
testinventory1: SSH auth method: private key
==> testinventory1: Machine booted and ready!
==> testinventory1: Checking for guest additions in VM...
==> testinventory1: Setting hostname...
==> testinventory1: Configuring and enabling network interfaces...
==> testinventory1: Mounting shared folders...
testinventory1: /vagrant => /tmp
$
Working as expected :)
On Monday, 21 October 2019 13:46:42 UTC+1, Jeremy Whiting wrote:
>
> Before running a Blog post example vagrant configuration I am stuck
> installing the provider plugin called virtualbox. Attempting to install the
> plugin fails. Due to a dependency conflict on ffi.
>
>
> $ vagrant plugin install virtualbox
>> Installing the 'virtualbox' 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:
>>
>> conflicting dependencies ffi (~> 1.0.9) and ffi (= 1.10.0)
>> Activated ffi-1.10.0
>> which does not match conflicting dependency (~> 1.0.9)
>>
>> Conflicting dependency chains:
>> ffi (= 1.10.0), 1.10.0 activated
>>
>> versus:
>> virtualbox (> 0), 0.9.0 activated, depends on
>> ffi (~> 1.0.9)
>>
>>
>> $
>>
>
> Is this error normal or error easily solved ?
>
> Details of my system. Fedora 30.
>>
>> $ vagrant box list
>> geerlingguy/ubuntu1404 (virtualbox, 1.2.12)
>> $ uname -a
>> Linux f30lite 5.2.17-200.fc30.x86_64 #1 SMP Mon Sep 23 13:42:32 UTC 2019
>> x86_64 x86_64 x86_64 GNU/Linux
>> $ vagrant --version
>> Vagrant 2.2.5
>> $ vagrant plugin list
>> vagrant-libvirt (0.0.45, system)
>> $
>>
>
> Blog post
>
> https://www.jeffgeerling.com/blog/creating-custom-dynamic-inventories-ansible
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/71031ed9-e3e2-4613-b0c6-a7bb13f72dd1%40googlegroups.com.
