Trellis: Vagrant up errors out due to unresolved dependenxy

[pajtai]

Submit a feature request or bug report

• [X] I've read the guidelines for Contributing to Roots Projects
• [ ] This is a feature request
• [X] This is a bug report
• [X] This request isn't a duplicate of an existing issue
• [X] I've read the docs and followed them (if applicable)
• [X] This is not a personal support request that should be posted on the Roots Discourse forums

Replace any X with your information.

Bug report

Please provide steps to reproduce, including full log output:

mkdir example.com && cd example.com
git clone --depth=1 [email protected]:roots/trellis.git && rm -rf trellis/.git\n
git clone --depth=1 [email protected]:roots/bedrock.git site && rm -rf site/.git
sudo vim /etc/hosts
cd trellis
vagrant up

results in:

Installing plugin vagrant-bindfs
Fetching: vagrant-bindfs-1.1.0.gem (100%)
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Unable to resolve dependency: user requested 'vagrant-vbguest (= 0.14.2)'

Please describe your local environment:

Ansible version: 2.4.3.0

OS: MacOS 10.13.2

Vagrant version: 2.0.2

Where did the bug happen? Development or remote servers?

Local Machine

Please provide a repository or your wordpress_sites config (if possible):

Full steps to repro are above.

Is there a related Discourse thread or were any utilized (please link them)?

[pajtai]

Looks like a vagrant plugin configuration issue. Resolved as follows:

--- example.com/trellis » vagrant plugin list
vagrant-bindfs (1.1.0)
vagrant-exec (0.5.2)
vagrant-hostmanager (1.8.7)
vagrant-vbguest (0.15.1)
--- example.com/trellis » vagrant plugin uninstall vagrant-vbguest

Now vagrant up runs. Looks like it was looking for an older version.

[clondon]

Hi, I know this is a late entry.
I have been trying Trellis and Root again after giving up with it a year ago.
I managed to overcome this error
"Unable to resolve dependency: user requested 'vagrant-hostmanager (= 1.8.7)'" by deleting the _~/.vagrant.d_ folder and running ### vagrant up again.
In this case, vagrant up installed the correct plugins and versions.
It then asks that you run vagrant up again and the magic started to happen successfully.

[kafoso]

Necro, but still relevant.

I fixed this by manually uninstalling "vagrant-hostmanager", and I suppose the same applies for "vagrant-vbguest", as OP mentions. I.e.:

vagrant plugin uninstall vagrant-hostmanager

Running vagrant destroy or vagrant up should install a working version of "vagrant-hostmanager".

---

Windows 10 Enterprise version 1809.
Vagrant 2.2.5.