I'm glad they have podman desktop. Personally though, once I realized that I can use the command line version without it (unlike docker in my experience) I uninstalled it as I don't really need the UI / KIND, etc. For me the command line is fine and having something where I don't have to first shell into wsl is great (it just runs it itself behind the scenes). Of course, Linux is generally better for development imo but this is a nice compromise on Windows.

▲

zenmac 7 hours ago | parent | next [-]

For mac, wouldn't it be just easier to use lima from cli? How does Podman compare to that? Docker unless on Linux has always being a bloat.

Or are there any lightweight hypervisor on top of firecracker alternative? At this point with the way systemd is going, we should just switch back to VM? Everything is just more mature on native OS install. Docker to Linux, just feels kinda like SPA reinventing the html parsing on top of a rendering engine.

	▲	wink 11 minutes ago \| parent \| next [-]
		I tried colima once and couldn't get it to do what I wanted. Maybe just a missing shim, maybe our setup with docker-compose for integration tests. (I'm usually on linux, so maybe my lack of mac experience also played a role) Zero problems with Podman Desktop.
	▲	jalk 4 hours ago \| parent \| prev \| next [-]
		Havn't tried Colima, but podman is very simple to use and smells like docker cli. On Apple Silicon machines however, latest podman version uses VM images which Rosetta doesn't work with, and hence it will use qemu for running amd64 containers. You can fix this by either installing podman 5.5 or create the VM from and older image [1]. My only complaint here is that the stock machine images are pretty large (~1G ) If you use containers to run tools that create files in your host (i.e. build tools), then you can use your host username as the default in the VM (machine init --username $(id -un)), and then run containers with --userns=keep-id. That way the the container command starts with the same username and uid as you host user - this is pretty tricky to get working with docker, from my experience. We use Bazel as our build tool and we create a lot of images based on shared layers. Bazel produces oci layout directories that contain descriptors and symlinks to the actual layer tars. Podman can start a container "directly" from these directories[2], which speeds up image testing considerably, since it can detect known layers immediately. With docker you have to stream a tarball with all the layers and descriptors to the docker daemon, only for it to discover that it already knows most of the layers. [1] https://docs.podman.io/en/latest/markdown/podman-machine-ini... - machine images https://quay.io/repository/podman/machine-os [2] podman run oci://<path to oci-layout-dir>
	▲	fruitplants 6 hours ago \| parent \| prev \| next [-]
		I used colima cli on M1-M2 Mac. A few memory related settings were required as some of old apps were huge. But apart from that it worked great. Nothing bad podman, just preferred colima.
	▲	seemaze 6 hours ago \| parent \| prev [-]
		Brew install podman? CLI only, no lima/colima or gui required.

▲

scuff3d 7 hours ago | parent | prev | next [-]

I'm the same. I just use Docker/Podman from the terminal. I know some people really like the GUI but I've never been able to find a workflow better than the cli with some scripts or compose.

Cool for Podman Desktop though.

▲

arcanemachiner 8 hours ago | parent | prev [-]

> unlike docker in my experience

You have piqued my curiosity. What does Docker Desktop do that the CLI cannot?

▲

pxc 7 hours ago | parent | next [-]

`docker machine` was deprecated in favor of Docker Desktop in order to funnel people towards paid licenses. But there's no real reason Docker on non-Linux should need a GUI.

	▲	shykes an hour ago \| parent [-]
		Hi, I'm the founder of Docker. The decision to launch Docker Desktop, and deprecate Docker Machine, had nothing to do with revenue. Desktop was free when we launched it in 2016, and it remained free until 2021. By then Docker had a new CEO, a new board, and I was gone. So the two events (launch and monetization) could not be more disconnected. The reason we launched Docker Desktop (initially known as "Docker for Mac") was to make the user experience better: easier to install, better integrated with the system (virtualization APIs, keychain, VPNs, etc), and better support for host volumes.

▲

danielnesbitt 8 hours ago | parent | prev [-]

Since they mention Windows, I believe this is a reference to the fact that you cannot (easily) install the Docker CLI without Docker Desktop. Podman does not have this issue.

	▲	no_carrier 6 hours ago \| parent [-]
		You absolutely can run docker on the CLI in WSL2. The only requirement is you have systemd running in your WSL distro, which is fully supported.