Hacker News Reader

Comment by conceptme | Hacker News Reader

It is mentioned in the article.

"Fast forward a couple of months, podman-machine is now deprecated in lieu of Vagrant"

That's not accurate. There was an older project called podman-machine, which is long gone. What you get when you use the `podman machine` command is a completely new implementation.

And it is built into the podman binary, as opposed to being a separate project.

I assume `podman-machine` is different than `podman machine`

See Marcos install https://podman.io/getting-started/installation

Also there are active issues and PR related to `podman machine`.

Yes, Red Hat reused the name - similar to the CoreOS name.

See https://boot2podman.github.io/2020/07/05/boot2docker-depreca... for the reasons why Vagrant was/is a workaround, after docker-machine and podman-machine stopped working.

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.

I don't think this is correct. They are currently working on a go based replacement (3.0).

Also vagrant by default depends on virtualbox, and that is x86-only so it does not work on your M1 Mac, or your Pinebook : )

I 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.

Vagrant was a workaround, before the new project got off the ground: 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.

Lima 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

Reply on news.ycombinator.com