Vagrant is approaching EOL. No more "Docker for VMs"

Re:Vagrant is approaching EOL. No more "Docker for VMs" by stasge on Tuesday September 08, 2026 @08:50PM (#49619292)

Lima give you a VM.

Vagrantfile gives you a repeatable and portable environment with just a few lines of configuration. Product demo? Pre-configured local Kubernetes? Clean build environment? Pre-cooked clean setups for 3rd party software projects? Everything is possible with just vagrant up -> vagrant ssh -> vagrant halt/destroy. There is no simple alternative.

[ Parent | on HN ]

Re:Vagrant is approaching EOL. No more "Docker for VMs" by bithavoc on Wednesday September 09, 2026 @10:36PM (#49637674)

I think I understand why, I used Vagrant for many years and this was my evolution:

* Vagrant for everything: VM provisioning(always local), os dependencies, app dependencies and the apps themselves was all Vagrant.

* Vagrant for VM provisioning and OS dependencies only. docker-compose for the rest

* Vagrant for VM provisioning, Rancher 1.6-ish for the rest

* Vagrant for VM provisioning and K3S for the rest.

* either k3s or docker-compose with no VM

so towards the end it was easy to replace Vagrant with whatever provisioned a VM

[ Parent | on HN ]