Trellis Drops Vagrant Support in Favor of Lima VMs

Trellis has removed support for Vagrant, VirtualBox, and Parallels for local development. Going forward, Lima VMs are the only supported option for running Trellis locally.

Since introducing Lima support, we’ve seen the difference firsthand. Every developer who has made the switch reports the same thing: Lima is faster, more reliable, and eliminates the constant friction of Vagrant’s NFS syncing.

Why we’re moving on from Vagrant

Vagrant has served the development community well for years, but it’s showing its age. It’s slow, requires multiple layers of abstraction, and relies on outdated virtualization solutions like VirtualBox and Parallels.

Lima represents the modern approach to local development VMs. On macOS, it leverages the native virtualization framework for dramatically faster performance. File system changes are instant.

What’s changing

Trellis no longer includes Vagrant configuration or support:

• Vagrantfile and Vagrant-related configuration have been removed from Trellis
• All local development now uses the trellis vm commands
• Vagrant and VirtualBox or Parallels are no longer required dependencies

Getting started with Lima

If you’re already using Lima with Trellis, nothing changes for you. Your existing setup will continue to work.

For those still on Vagrant, migrating is straightforward:

1. Destroy your existing Vagrant box: vagrant destroy
2. Start your VM with Lima: trellis vm start

Your existing Trellis configuration remains unchanged. The trellis vm commands work seamlessly with your current setup.

Questions or feedback?

Head over to Roots Discourse to share your experience with the migration or ask any questions. If you run into any issues, please report them on the trellis-cli repo.