I finally replaced Docker Desktop with a more tweakable, terminal-friendly alternative

Published Oct 18, 2026, 7:00 AM EDT Arol is a tech journalist who currently works as a contributor at How-To Geek since 2022. He first began writing online for the short-lived portal of Spanish-language gaming forum Emudesc in 2013. Years later, in 2017, he got his true start in tech journalism working for a small Google-focused site called Pixel Spot. He transitioned to a news and feature writer role at XDA Developers that same year, where he worked until 2021 before making the jump to other websites. Arol brings nearly a decade of writing experience, and the occasional hot take, to his writings. While he's a technology lover at heart, he holds computer hardware and smartphones particularly close to heart. You'll normally find him covering news, although he has also written the occasional deal, buyer's guide, how-to post, and round-up. He's also written for Android Police and MakeUseOf. He's also a Political Science student at the Central University of Venezuela, and a proud member of student movement Àgora UCV. When he's not writing, you'll probably find him hitting the gym, trying to ace a new hobby, reading his textbooks, or traveling. You can reach him at me@arolwright.com. Docker Desktop is the default way to run containers on a Mac, but it is not the only one. Colima, a free open-source runtime driven entirely from the terminal, offers a lighter and more configurable alternative. Here is what it is, how it compares, and who should switch. What’s Colima? A command-line way to run containers on a Mac Colima is an open-source tool that runs container runtimes on macOS and Linux with as little setup as possible. The name stands for Containers on Lima, a reference to the Lima project, which launches lightweight Linux virtual machines. Colima wraps that machinery in a simple command-line interface, so a single command boots a small Linux VM and configures everything your Mac needs to talk to it. By default, Colima uses Docker as its runtime, which means the regular docker client works once the VM is up. The client is a separate install, usually through Homebrew, and after you run colima start, commands like docker ps and docker run behave the way they always have. Colima also supports containerd, which you can drive with nerdctl, and Incus for system containers and virtual machines. Kubernetes is available as an optional add-on for the Docker and containerd runtimes, switched on with a single flag. The project is released under the MIT license and runs on Intel and Apple Silicon Macs as well as Linux. It can be installed through Homebrew, MacPorts, Nix, and Mise. Out of the box, it handles port forwarding and volume mounts automatically, two chores that often trip up newcomers to VM-based container setups. It can also run several isolated instances side by side, which is handy when different projects need separate environments. Colima is not an obscure experiment. Its GitHub repository has passed 30,000 stars, and Thoughtworks has called it a go-to alternative to Docker Desktop on macOS. What it deliberately lacks is a graphical interface. There is no dashboard, no tray icon, and no extension marketplace. Everything happens through commands and a configuration file, which is exactly the appeal for people who already live in a terminal. Why is it better? Lower costs and finer control over your container VM The first argument is cost. Docker Desktop is free for personal use, education, non-commercial open-source work, and small businesses with fewer than 250 employees and under $10 million in annual revenue. Larger companies need a paid subscription for commercial use. Colima is MIT-licensed and free for everyone, which takes licensing out of the conversation entirely. The second argument is control. The default VM is modest, with two CPUs, 2 GiB of memory, and 100 GiB of storage, but you can change those numbers with flags such as --cpu, --memory, and --disk, or by running colima start --edit to open a configuration file. Resizing an existing VM means stopping it and starting it again with new values, although disk space can be increased after creation. Because the VM is only as large as you make it, you decide how much of your machine the container runtime is allowed to use. Apple Silicon owners get further options. Colima can use Apple’s virtualization framework with Rosetta 2 emulation, which helps when you need to run x86 images. It also supports GPU-accelerated containers for AI workloads through the krunkit VM type, a feature that requires Apple Silicon and a recent version of macOS. Multiple instances let you keep, for example, a Kubernetes-enabled environment apart from a plain Docker one. The third argument fits. Because Colima is a command-line tool, it slots easily into dotfiles, shell scripts, and setup automation. It starts when you ask it to and stops when you don’t need it, instead of sitting in the menu bar as a full desktop application. Whether that makes it better depends on what you value, but for people who want a runtime that stays out of the way, the case is a strong one. Should you use it? Great for terminal users, less so for everyone else Colima makes the most sense for developers on macOS or Linux who are comfortable in a terminal and want a lean container setup. If your employer has more than 250 employees or crosses the revenue threshold, it also offers a way to run Docker-compatible workflows without paying for Docker Desktop, though it is worth checking your company’s policies before switching. Developers who want local Kubernetes, containerd parity with managed cloud services, or several isolated environments will find plenty to like. There are trade-offs. Colima supports only macOS and Linux, so Windows users are out of luck. It has no graphical dashboard, which can feel like a step back if you rely on a visual overview of containers, images, and volumes. Docker Desktop’s extras, such as its extensions and the hardening and registry controls in its business tiers, have no direct equivalent. You also need to install the Docker client yourself, and changing CPU or memory means restarting the VM. Switching is low-risk, which is the best reason to try it. Installation takes a single Homebrew command, and colima start brings up a working Docker environment in moments. Because Colima works with the standard docker client, your existing Dockerfiles and Compose files should generally carry over, although it is sensible to test any setup that depends on specific volume or networking behavior. Spending a week with it before uninstalling anything is an easy way to find out whether it fits. Colima is a free, lightweight alternative for terminal-savvy developers Colima trades Docker Desktop’s polish for freedom, flexibility, and a smaller footprint. It suits terminal-comfortable developers on macOS or Linux, especially at larger companies facing licensing costs. If you need a graphical interface or Windows support, stay put; otherwise, it deserves a trial run.