My understanding is that this old article is no longer the simplest/easiest way of doing this. For that, see <a href="https://marcusnoble.co.uk/2021-09-01-migrating-from-docker-to-podman/" rel="nofollow">https://marcusnoble.co.uk/2021-09-01-migrating-from-docker-t...</a>. tl;dr:<p><pre><code> $ brew install podman
$ podman machine init
$ podman machine start
$ alias docker=podman
</code></pre>
If you're on an M1 you may run into <a href="https://github.com/containers/podman/issues/10577" rel="nofollow">https://github.com/containers/podman/issues/10577</a> (which is WIP, and may have been resolved by <a href="https://github.com/containers/podman/pull/11451" rel="nofollow">https://github.com/containers/podman/pull/11451</a>).
Is there any practical benefit of Podman over Docker on a Mac? Virtual machine is still needed, so any performance issues are likely to persist (well, maybe Docker for Mac is a bit more buggy, but we can manually setup Docker instead of Podman in a similar way).<p>Also, I think we are losing here access to the Docker socket on the host (inside the virtual machine it can be emulated using docker-podman).
This feels like the whole industry is now all going through the same motions…<p>I tried podman; two hurdles I haven't figured out: 1/ sending the context is <i>incredibly</i> slow on podman, compared to Docker+Buildkit. It's definitely trying to send literally the entire context, like Docker without Buildkit does, but even more slowly… 2/ private registry auth. Haven't really tried too hard, but it's not just "a drop in replacement"; I think I need to somehow auth with podman specifically. (Part of this is our external registry is ACR, and we auth with `az`, but I think `az` is presuming Docker…)
While there do exist several alternatives to Docker Desktop, I am a fan of multipass. Something I don't see anyone talking about, the host to guest volume mounting performance can't be beat. The alternatives can't hold a candle to Docker Desktop's solution.<p>I need this volume mounting to get development code changes into the container in a reasonable time and the alternative performance feels like running on a standard hard drive compared to nvme ssd.
Is Vagrant still actively used? I was all over it some 4-5 years ago.<p>I remember HashiCorp even favoring a newer product they were trying to promote.
How does this compare to multipass? I tried multipass out on an Intel Mac yesterday and it worked great until I connected to corporate vpn (anyconnect) and then it all went downhill. Tried some of the workarounds (<a href="https://multipass.run/docs/troubleshooting-networking-on-macos#network-routing-problems" rel="nofollow">https://multipass.run/docs/troubleshooting-networking-on-mac...</a>) but no luck. Back to Docker Desktop.
Is there is a solution for using `docker-compose` on mac with podman? I know that podman supports it natively now, and there is `podman-compose`, but I couldn’t find much on getting either working on a mac due to the remote setup.
Does Podman do a better job avoiding bloat in the development workflow? That’s been a major thing with docker for me, it spins up a new layer whenever I try to do send an arbitrary command to a running vm, which with development (PHP) I find this is something I have to do often, so these layers add up quickly
I tried podman on my MBP and didn't get very far :/ <a href="https://github.com/containers/podman/issues/11479" rel="nofollow">https://github.com/containers/podman/issues/11479</a>
See <a href="https://news.ycombinator.com/item?id=28379556" rel="nofollow">https://news.ycombinator.com/item?id=28379556</a> for a recent discussion about minikube (the only drop-in replacement for Docker Desktop).
We replaced Docker hub with ghcr + buildah action and we won't ever look back! We are just waiting for more compose support which seems that will happen shortly anyway.<p>Thanks redhat!
best thing about podman is the -l option, that refers to last image used<p>for example to see the last conatainer's logs:<p>podman logs -l<p>just beautiful!