Though I think I managed to fix it. Just need further testing, that will probably do tomorrow or at last this weeked.
I checked the install location for the ruby libraries, where the current libruby.so resides /usr/lib/libruby.so, which is actually a link:
ll /usr/lib/libruby.so
lrwxrwxrwx 1 root root 16 Aug 22 01:16 /usr/lib/libruby.so -> libruby.so.2.7.1
So what I did is trick vagrant into thinking he is using the “older version” via making a symlink to the current version of libruby.so
sudo ln -s /usr/lib/libruby.so /usr/lib/libruby.so.2.4
Ad the result is:
ll /usr/lib/libruby.so.2.4
lrwxrwxrwx 1 root root 19 Sep 23 23:14 /usr/lib/libruby.so.2.4 -> /usr/lib/libruby.so
This will probably be some kind of temporal fix, as once rubylib updates it’s major version, my vagrant my start breaking up due to deprecated methods etc…
I will keep posted any future changes that may arise on this. But as of today, it has been “patched/fixed”