Closed kyleskrinak closed 8 years ago
Hi @kyleskrinak
You are not the first reporting this issue. Looks like vagrant did something wrong in their last version which brought a retro-bug.
Looks like downgrading to VirtualBox 5.0.20 and vagrant 1.7.4 solves the issue.
@achekulaev Thanks for the suggestions. I did try the vagrant vbguest plugin before I posted. However, I get this message:
The guest's platform ("tinycore") is currently not supported, will try generic Linux method...
which leads to
An error occurred during installation of VirtualBox Guest Additions 5.1.2. Some functionality may not work as intended.
I also previously tried vagrant ssh
into the b2d machine to run this command:
sudo ln -s /opt/VBoxGuestAdditions-4.3.10/lib/VBoxGuestAdditions /usr/lib/VBoxGuestAdditions
which I presume should be
sudo ln -s /opt/VBoxGuestAdditions-5.1.2/lib/VBoxGuestAdditions /usr/lib/VBoxGuestAdditions
Or whichever version of VBox I'm running. However, the b2d machine only lists
bootlocal.sh
bootscript.sh
bootsync.sh
shutdown.sh
tcemirror
There's no such dir in /opt.
I'm using Drupal VM until I resolve this, but really miss drude.
Have you tried downgrading to VirtualBox 5.0.20 and vagrant 1.7.4?
I had only downgraded VB previously. Downgrading both did the trick. Thanks! Drupal VM is nice, but way overkill, storage-wise.
Great!
I will keep this issue open and update it once it's safe to update to the latest versions. Going forward we'll get rid of Vagrant.
This is a duplicate of https://github.com/blinkreaction/drude/issues/155
Closing in favor of the issue in the upstream project: https://github.com/blinkreaction/boot2docker-vagrant/issues/83
Let's move further discussions there.
This post me helped Link solve this problem.
I ran:
which, most notably, updated my VBox to 5.1.2, which I've now learned is an issue with Vagrant, as per this ticket #155
So I've downgraded my VBox to 5.0.20 (which it was at prior to the upgrade) however, I am seeing this error:
shelling into the b2d box, I run
and see:
Only a partial list of what should be running.
I'm unclear of what I can do next to get my drude environment operational again?