If your deployment target is a VM/bare-metal rather than container, Vagrant makes a lot of sense for development. E.G. my dev Vagrantfile fits in a small scree

If your deployment target is a VM/bare-metal rather than container, Vagrant makes a lot of sense for development. E.G. my dev Vagrantfile fits in a small screen, and provisioning is handled by a single Ansible playbook that works for all environments (using conditionals). So there's no need to maintain a separate dev container, and a lot of subtle headaches are avoided in the deployment process Setting up the dev environment consists of running `vagrant up` (assuming Vagrant/Ansible are installed). That's it. You get all the benefits of IaC (fast ~reproducible dev) without shoehorning containers in.