It seems to me that almost no one understands the difference between the various layers of "Docker" (that is to say: Desktop, CLI, daemon, containerd, runc) and which layers tools like Podman aim to replace.
This is how Podman fits in:
Podman (and its various components) can replace everything but parts of Docker Desktop, namely the GUI that Docker Desktop, has. For everything else, it has it's own Docker compatible CLI, an optional daemon (by default it's daemonless), there is no containerd component as it communicates directly to any OCI compatible runtime. They've also implemented their own OCI compatible runtime, crun, which is supposed to be faster than runc, and more lightweight.
I suppose for the average Joe/Jane this probably doesn't matter. They want to run a few commands the first time around to set up, and then do "start/stop/remove my container" and that's all they want to do.
EDIT: github link: https://github.com/containers/podman/issues/8016
According to a post on the podman website: "Current implementation relies on qemu which currently has some platform dependencies." [1]
I also just checked on my machine and it is indeed running on Qemu.
IIRC Qemu also has support for Apple's Hypervisor.framework.
[1] https://podman.io/community/meeting/notes/2021-04-06/#podman...
Looks like they are adding it https://twitter.com/glours/status/1438526841577357315
I quote: "A dream coming true for a lot of #linux users, @dieuthicao announced that we’ll start working on a #Linux version of @docker Desktop"
As a Linux user, far from a dream at all, really.
ETA: Oh hey here it is: https://github.com/heyvito/podman-macos
> ETA: Oh hey here it is: https://github.com/heyvito/podman-macos
This GUI isn't an official Podman application. It's a third party. Not that it's bad or anything, it's just not official.
Except for:
- Docker Compose (because podman-compose has a large amount of open issues https://github.com/containers/podman-compose/issues)
- Docker Swarm (since Docker provides a lightweight orchestrator out of the box), you'd need to use something like K3s or another Kubernetes distro
- anything that uses the Docker socket (/var/run/docker.sock), so you can forget about running anything like Portainer or any of the other tools out thereSee for example: https://www.redhat.com/sysadmin/podman-docker-compose
Of course, there's no Swarm support, as evidenced by that very article:
> Caveats
> One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman.
Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/
Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman
https://docs.docker.com/machine/
For now however, you can use minikube which provides drivers for Hyper-V and hyperkit:
Linux, yeah, I don't think there is a Desktop version for that. It's all CLI