Vagrant environment issues

I am having problems with the Vagrant environment while working on “Homework 1.2 : Enabling Authentication on a Running Replica Set”.

When I try to run this command:

…:m310-vagrant-env me$ vagrant up

I get this result:

Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190514.0.0’ is up to date…
==> database: Machine already provisioned. Run vagrant provision or use the --provision
==> database: flag to force provisioning. Provisioners marked to run always will still run.
==> infrastructure: Checking if box ‘centos/7’ version ‘2004.01’ is up to date…
==> infrastructure: Clearing any previously set forwarded ports…
==> infrastructure: Fixed port collision for 22 => 2222. Now on port 2200.


==> infrastructure: Checking for guest additions in VM…
infrastructure: No guest additions were detected on the base box for this VM! Guest
infrastructure: additions are required for forwarded ports, shared folders, host only
infrastructure: networking, and more. If SSH fails on this machine, please install
infrastructure: the guest additions and repackage the box to continue.
infrastructure:
infrastructure: This is not an error message; everything may continue to work properly,
infrastructure: in which case you may ignore this message.
==> infrastructure: Setting hostname…
==> infrastructure: Configuring and enabling network interfaces…
==> infrastructure: Rsyncing folder: /Users/me/Documents/Exploration_Space/m310-vagrant-env/ => /vagrant
==> infrastructure: Mounting shared folders…
infrastructure: /home/vagrant/shared => /Users/me/Documents/Exploration_Space/m310-vagrant-env/shared
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem “vboxsf” is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 home_vagrant_shared /home/vagrant/shared

The error output from the command was:

mount: unknown filesystem type ‘vboxsf’

…:m310-vagrant-env me$

Since I was able to use Vagrant in one previous exercise, I suppose it should be working.
But I may also well be doing some basic mistakes, since I had never heard of it before taking this course.

May be version related issues

Vagrant up fails on mount of ‘vboxsf’

Please check other threads.Another student had same problem last week

Thanks but that does not apply.

I have version 2.2.13. It seems to be the latest version for the Mac.

And in the post you refer to, they are talking about version 2.2.4.

What is the current status of vagrant
Did you try to bringup infrastructure?
or destroy infrastructure and bring it up after plugin is installed

I tried vagrant destroy in a bunch of different ways and then vagrant up again.
And now it seems to be working. I am not totally sure of what made it work and I am not sure it will keep working for ever. As I remember it looks like when running vagrant destroy I need to remove the database and keep the infrastructure.