Is Vagrant commonly used in DevOps?

Vagrant shows up in DevOps-adjacent workflows, but calling it "widely used in DevOps" overstates its role. HashiCorp released Vagrant in 2010 to solve one problem: reproducible local development and test environments defined in a Vagrantfile. That's still where it lives, not in the production pipeline.

Where the "DevOps tool" label comes from

Vagrant pairs with provisioners like Ansible, Puppet, Chef, or plain shell scripts to configure a VM after it boots. Because that provisioning step looks like infrastructure-as-code, and because teams often mention Vagrant in the same breath as Docker or Terraform when describing their local setup, it gets grouped under the DevOps umbrella. The confusion is that "used alongside DevOps tools" gets read as "a DevOps tool," when Vagrant's actual job is standing up a full virtual machine on a laptop, not managing infrastructure that ships to production.

How much is it actually used?

Docker took over most of the ground Vagrant used to cover. Containers start faster, use less memory, and match production more closely than a VM does, so teams that once used Vagrant purely to avoid "works on my machine" problems mostly moved to Docker Compose or dev containers. Vagrant's remaining use cases are narrower and more specific: multi-VM network simulation, testing against a real kernel or OS that a container can't emulate, onboarding environments for teams with legacy stacks, and some Windows or BSD development where containerization isn't practical. Docker, Kubernetes, Terraform, and CI/CD pipelines are the tools that actually run production delivery, while Vagrant sits a layer below that, at the workstation.

What this means for hiring

Vagrant experience on its own doesn't tell you much about someone's production DevOps skills, and its absence isn't a gap worth worrying about. A developer who lists Vagrant as a primary tool, with no Docker, Kubernetes, or Terraform alongside it, is more likely describing legacy or VM-heavy infrastructure work than current container and cloud delivery experience. If the role needs someone who can build and operate a CI/CD pipeline or manage containerized services, ask directly about those tools rather than inferring capability from Vagrant on a resume.