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
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…
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.
Minikube is more similar to Docker Toolbox, which is not too surprising - considering they are built on the same Docker Machine. Which Docker Inc. doesn't want to support anymore, saying that it was replaced with Docker…
minikube now includes a command called "minikube image build", which builds the images for your Kubernetes cluster - for any container runtime, including docker - but also containerd
I updated the README based on feedback from here... Once there is any documentation or blog post for the new podman machine feature, I will link directly to it
The comments were regarding two different projects, one is deprecated (old podman-machine) one is not (new podman machine)
It's a "work in progress", basically an updated version of the old projects that serve like a proof-of-concept if you can tolerate the old versions (docker 19.03 and podman 1.9.3) The runs from RAM is an integral part…
I added some clarification (hopefully) to the README, it gets a bit confusing when terms like "Machine" and "CoreOS" get reused
Then you will be glad to hear that I was planning to continue the podman-machine project, but under a different name... https://boot2podman.github.io/2021/01/24/reboot-new-project....
I will "unlock" the deprecated boot2podman projects and add some more text about it to the README.
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
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…
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.
Minikube is more similar to Docker Toolbox, which is not too surprising - considering they are built on the same Docker Machine. Which Docker Inc. doesn't want to support anymore, saying that it was replaced with Docker…
minikube now includes a command called "minikube image build", which builds the images for your Kubernetes cluster - for any container runtime, including docker - but also containerd
I updated the README based on feedback from here... Once there is any documentation or blog post for the new podman machine feature, I will link directly to it
The comments were regarding two different projects, one is deprecated (old podman-machine) one is not (new podman machine)
It's a "work in progress", basically an updated version of the old projects that serve like a proof-of-concept if you can tolerate the old versions (docker 19.03 and podman 1.9.3) The runs from RAM is an integral part…
I added some clarification (hopefully) to the README, it gets a bit confusing when terms like "Machine" and "CoreOS" get reused
Then you will be glad to hear that I was planning to continue the podman-machine project, but under a different name... https://boot2podman.github.io/2021/01/24/reboot-new-project....
I will "unlock" the deprecated boot2podman projects and add some more text about it to the README.