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

(developer.hashicorp.com)

19 points | by stasge 2 days ago ago

9 comments

  • fwilhe 2 days 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 a day 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 a day ago

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

  • roryirvine 2 days 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 a day ago

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

  • stuaxo a day ago

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

    • stasge a day ago

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

  • a day ago
    [deleted]
  • chris_fa__ 10 hours ago

    [flagged]