colima

After docker desktop became unusable, I jumped to colima and never looked back. I still use the docker runtime in it (the non-proprietary part) but it also supports containerd. On Mac it's just a "brew install colima" and then "colima start" I also install the compose and ecr credentials plug-ins (since I use ecr for my container registry.) It has the full functionality of docker desktop minus the UI, which I never used anyways. https://github.com/abiosoft/colima

"colima" and it's underlying project "lima" are a pretty quick way to get started. Extremely quick to stand up a single node cluster, or many types of VMs in lima. https://github.com/lima-vm/lima limactl start template://k3s https://github.com/abiosoft/colima colima start --kubernetes The tools are a bit rough around the edges if you try and do something outside of the happy path with them. Nothing bad as such, just the user experience isn't as seamless when say running the VMs on custom, addressable host networks or managing vms with launchd.

I'd say Lima and Colima should be enough for most use cases: https://lima-vm.io/ https://github.com/abiosoft/colima

Try Colima [0], it’s a CLI only Docker Desktop replacement built on Lima. [0] https://github.com/abiosoft/colima

I've been using Colima (which uses Lima, and QEMU under the hood) and it works fine for me. https://github.com/abiosoft/colima

I like lazydocker, but I really wish it understood Docker contexts without having to set `$DOCKER_HOST`. I switch between Colima[0] and OrbStack[1] and have multiple Colima virtualization profiles[2] (one with `vz`, one without), resulting in multiple Docker contexts. I have a function that I’ve written to set docker host, but I have to remember to clear it after I’m done using lazydocker and a couple of other tools (dive, I think). function set-docker-host command -sq docker and command -sq jq or return 1 set -l host ( docker context ls --format '{{ . | json }}' | jq -sr '.[] | select(.Current == true) | .DockerEndpoint' ) or return 1 set -gx DOCKER_HOST $host end The bash/zsh equivalent wouldn't be too hard, but I use fish. [0] https://github.com/ab

Lima wraps QEMU in a simple CLI, with neat features for container users, such as filesystem sharing and automatic localhost port forwarding, as well as DNS and proxy propagation for enterprise networks. Rancher Desktop wraps Lima with k3s integration and GUI. * Github: https://github.com/lima-vm/lima * Talks: https://github.com/lima-vm/lima/blob/master/docs/talks.md Also see * sshocker: ssh + reverse sshfs + port forwarder, in Docker-like CLI (predecessor of Lima), https://github.com/lima-vm/sshocker * Lima-GUI: https://github.com/afbjorklund/lima-gui * Colima: https://github.com/abiosoft/colima

One more caveat: mounts don't work: https://github.com/abiosoft/colima/issues/503 One of our tools runs in Docker just to ensure that it gets the right version of its dependencies, and that bug is a pretty huge bug for us, for that tool, as it basically broke things. Still, we use colima; it is a decent workaround for the "Docker on macOS" problem otherwise.

Also worth checking out is Colima, which uses Lima to give you a linux container environment without needing to install Docker Desktop: https://github.com/abiosoft/colima

Also: https://github.com/abiosoft/colima https://github.com/rancher-sandbox/rancher-desktop

No and yes (via docker-cli, the open source part) https://github.com/abiosoft/colima/issues/627

Mind the clock drift. https://github.com/abiosoft/colima/issues/274

Try out Colima[0]. I saw someone else mention it on here a few months ago and thought to try it and it's been very good. I did encounter my first problem yesterday so I have moved back to Docker Desktop for now but even if it only worked half the time I'd still suggest it, the memory usage is under a quarter of Docker's offering! [0] https://github.com/abiosoft/colima

After opening it, the first thing it does is to offer to opt-out of telemetry. That's good enough. That said, after I denied it, when I go to Settings it says Telemetry: Enabled, even though the checkbox to enable it is unchecked. I have no idea which reflects my current settings. Furthermore, after I selected to "Initialize Podman", the switcher is still in the "off" position. If I click it again, it says the VM already exists. I'm not sure how to stop it, or if it's even actually running. I'll stick with colima [0] for now as it's simple, easy, with not telemetry, and I always know what's its state. [0] https://github.com/abiosoft/colima