# Problems with VM and ansible when running Vagrant Provision

**URL:** https://discourse.roots.io/t/problems-with-vm-and-ansible-when-running-vagrant-provision/13643
**Category:** trellis
**Created:** 2018-09-19T17:24:09Z
**Posts:** 8
**Showing post:** 4 of 8

## Post 4 by @fullyint — 2018-09-22T23:28:14Z

> [@brightsite](#):
>
> a project that was built last year with Sage/Trellis/Bedrock.

> [@brightsite](#):
>
> I’ve checked the version of Ansible… it’s 2.6.4

If your project’s Trellis version is a year old, you’ll probably need to roll back your Ansible version to be compatible.

Options to find the Ansible version appropriate for your Trellis project:

- Check your project’s `CHANGELOG.md` for the most recently mentioned Ansible version
- Older Trellis: `roles/common/defaults/main.yml`
- More recent Trellis: `lib/trellis/plugins/vars/version.py`

Notes on [installing older Ansible versions](https://discourse.roots.io/t/i-am-encountering-this-error-and-need-to-address-it-in-about-20mins-error-unexpected-exception-this-is-probably-a-bug-no-module-named-six/12704) (see entire thread)

Somewhat related discussion for [compatibility between Ansible versions and Trellis](https://discourse.roots.io/t/trellis-invalid-vars-plugin-version-errror-with-ansible-2-4-0-0/10671/5)

* * *

When I google errors such as `Adding box 'base' (v0) for provider: virtualbox **` and `Couldn't open file /** /base`, I see suggestions that you have created your own Vagrantfile instead of just using the one included with Trellis. This could happen if you `vagrant init` somewhere, or perhaps if you `vagrant up` from a directory other than your Trellis project.

---

_[View the full topic](https://discourse.roots.io/t/problems-with-vm-and-ansible-when-running-vagrant-provision/13643)._