4 ms·
So is a Vagrant-based alternative the current solution? Vagrant seems like it's long been a 'maintenance only' project for Hashicorp, though not abandoned at le
by geerlingguy 5y ago
So is a Vagrant-based alternative the current solution? Vagrant seems like it's long been a 'maintenance only' project for Hashicorp, though not abandoned at least.
- inyorgroove 5y agoI don't think this is correct. They are currently working on a go based replacement (3.0).
- roywashere 5y agoAlso vagrant by default depends on virtualbox, and that is x86-only so it does not work on your M1 Mac, or your Pinebook : )
- mnutt 5y agoI believe there are hypervisor.framework backends for vagrant, but it seems that for whatever reason they haven’t taken off? I’m not exactly sure why they haven’t become the default on Mac, given how much more efficient it presumably is.
- afbjorklund 5y agoVagrant was a workaround, before the new project got off the ground: https://boot2podman.github.io/2020/07/22/machine-replacement.html https://boot2podman.github.io/2020/07/22/machine-replacement... Any virtualization solution could be used, with some more typing (like running the shell commands directly). It's not unique to Vagrant.
- afbjorklund 5y agoLima is a new and better option for this, it does not use a bundled Ruby runtime and does not use anything from Oracle. Just Go and QEMU... See https://github.com/lima-vm/lima https://github.com/lima-vm/lima