3 ms·
Vagrant is approaching EOL. No more "Docker for VMs"
- roryirvine 24d agoI think this is just the cloud-hosted registry - the good old cli remains available, albeit under the non-free Business Source License: https://github.com/hashicorp/vagrant https://github.com/hashicorp/vagrant
- stasge 24d agoIt's like Docker without public registries, nobody is going to use it
- fwilhe 24d agoI replaced my vagrant usage with lima-vm due to the license change years ago and I'm happy with it https://lima-vm.io/ https://lima-vm.io/ Lima is a great tool for simple quick or for automated repeatable virtual environments!
- idontneedcoffee 24d agoHow exactly did the license change affected your particular use-case?
- stasge 24d agoLima 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.
- bithavoc 23d agoI 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
- stuaxo 24d ago"Docker for VMs" it's what we used before docker.
- stasge 24d agoDocker is not a replacement though, you can't use Docker as a VM, not without workarounds, limitations and caveats.
- deleted 24d ago[deleted]
- chris_fa__ 23d ago[flagged]