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

Vagrant is approaching EOL. No more "Docker for VMs"(developer.hashicorp.com)

17 points by stasge 1 day ago | 7 comments

fwilhe 19 hours ago |

I replaced my vagrant usage with lima-vm due to the license change years ago and I'm happy with it https://lima-vm.io/

Lima is a great tool for simple quick or for automated repeatable virtual environments!

stasge 5 hours ago | |

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.

idontneedcoffee 9 hours ago | |

How exactly did the license change affected your particular use-case?

roryirvine 21 hours ago |

I 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

stasge 5 hours ago | |

It's like Docker without public registries, nobody is going to use it

stuaxo 16 hours ago |

"Docker for VMs" it's what we used before docker.

stasge 5 hours ago | |

Docker is not a replacement though, you can't use Docker as a VM, not without workarounds, limitations and caveats.