There's a feature request for Vagrant support: https://github.com/orbstack/orbstack/issues/105

Hasn't been that common of a request, and honestly I've never used Vagrant so not familiar with its benefits. People are already using OrbStack machines and its "orb" command to build dev envs with setup scripts, and cloud-init support will also be added: https://github.com/orbstack/orbstack/issues/38

I think cloud-init will be more useful since it's already widely used for setting up servers, whereas Vagrant is only for dev envs, but correct me if I'm wrong.

Plenty of companies use Vagrant. OrbStack's pricing is almost as much as an annual Parallels license for each of our devs. Most places using Vagrant will be using VirtualBox on Intel, or Parallels on Apple Silicon. So you haven't seen many requests because Vagrant users already have a solution and OrbStack wouldn't save enough money to ever switch to it.

As much as I think you should support Vagrant in your tool, that isn't the point I was making - whether it's worth supporting is something you need to decide for yourself.

The point I was making is this: Your claim is

> No matter the use case, OrbStack has you covered with features

But you don't support a common, cross-platform tool that's been around for ages and is used for managing developer environments - including running containers.

We looked at Orbstack, saw that there is no Vagrant support, and moved on.

I'll bet there are many other companies with a similar thought.

Orb stack is too young to warrant piling on the tickets, vs just assuming it is immature.

Fair. Another part of it is that I'm more focused on containers at the moment.