Colima vs OrbStack vs Docker Desktop: Running Docker on Mac Without Selling Your Soul

Docker Desktop Ate My MacBook and I Want a Refund

There’s a special kind of pain that Mac developers know well. You open Docker Desktop, watch the little whale icon bounce in your dock for 45 seconds, check Activity Monitor, and realize that running a single Postgres container is consuming more RAM than your entire college laptop had. Your fans spin up like a 737 on takeoff. Your MacBook Pro gets warm enough to keep coffee hot. And somewhere in Cupertino, a single tear rolls down a MacBook engineer’s cheek.

Docker on Mac has always been a hack. Unlike Linux, where Docker runs natively, macOS needs a Linux VM to host the container runtime. Docker Desktop has been handling that VM for years, and it’s gotten… comfortable. Maybe too comfortable. Like a houseguest who started using your Netflix and never left.

Then came the 2022 licensing drama. Docker Inc. announced that Docker Desktop was no longer free for companies with more than 250 employees or $10M in revenue. Suddenly, every engineering org had to either pay up or start looking for alternatives. That’s when the Mac Docker ecosystem got interesting.

So here we are in 2026, with three serious contenders: Docker Desktop (the bloated OG), Colima (the CLI nerd’s choice), and OrbStack (the polished newcomer). Let’s break them all down.

The Contenders

Docker Desktop: The One That Started It All

Docker Desktop is what most Mac developers reach for because it’s what the tutorials say to install. It bundles everything: the Docker daemon, Docker Compose, a Kubernetes cluster, a GUI dashboard, and approximately 4GB of RAM usage to run hello-world.

That last part isn’t even a joke. On a fresh M2 MacBook Pro, Docker Desktop idles at around 3-4GB of RAM before you’ve started a single container. The VM it runs is a full Linux kernel with no concept of “maybe don’t use all the memory.”

The good: It just works. Extensions, GUI, built-in Kubernetes, excellent documentation, enterprise support. If you’re onboarding junior devs who’ve never touched Docker, Desktop gets them running in 10 minutes with zero terminal trauma.

The bad: Resource usage that would embarrass a Windows 11 VM. Startup times of 30-60 seconds cold. And the licensing — $21/month per user for the Pro plan, with Business plans going higher.

Installation:

# Download from docker.com/products/docker-desktop
# Or via Homebrew:
brew install --cask docker

After install, open it from Applications and go make a coffee. Seriously.

Colima: The “I Don’t Need a GUI” Special

Colima stands for Container Linux on Mac. It uses Lima (Linux Machines) under the hood to spin up a lightweight VM, then runs the Docker (or containerd) daemon inside it. No GUI. No electron app. Just a terminal command and a very efficient VM.

This is the option for people who learned Docker on Linux and are mildly offended that their Mac needs a 4GB VM to run containers. Colima respects your resources. It’s free, open-source, and configurable down to CPU cores and memory allocation.

The good: Lightweight, free forever, rootless mode support, configurable VM specs, supports both Docker and containerd, works great with Docker Compose. If you know what you’re doing, this is excellent.

The bad: No GUI (a pro for some, a con for others). Initial setup requires a bit more CLI comfort. Kubernetes support exists but is less polished. Debug tooling is more DIY.

Installation:

brew install colima docker docker-compose

# Start with custom resources (don't let it default-allocate everything)
colima start --cpu 4 --memory 6 --disk 60

# Check it's running
docker ps

# Stop when you're done (this is the big win — you control the lifecycle)
colima stop

RAM at idle: roughly 600MB-1.2GB depending on your VM config. Startup time: 20-35 seconds first time, 10-15 seconds after that. Cost: free.

One workflow tip: add an alias so you don’t accidentally use Docker Desktop’s socket:

# In your .zshrc
export DOCKER_HOST="unix://${HOME}/.colima/default/docker.sock"

Colima also lets you run multiple profiles, which is genuinely useful if you want separate environments for different projects:

colima start --profile work --cpu 4 --memory 8
colima start --profile home --cpu 2 --memory 4
colima list  # see all running instances

OrbStack: Fast, Native, and Slightly Suspiciously Good

OrbStack showed up and immediately made Docker Desktop fans feel bad about their life choices. It’s a native macOS app, meaning it’s not an Electron wrapper over a Linux GUI — it’s actually built for Mac. On Apple Silicon, it uses macOS’s Virtualization framework directly, which means startup times measured in seconds, not minutes.

We’re talking 3-5 seconds to be running containers. On an M3 MacBook Pro, OrbStack cold-starts in under 3 seconds. Compared to Docker Desktop’s 45-60 second startup, it feels like the difference between booting a PC from a spinning hard drive versus an NVMe SSD.

The good: Fastest startup of any option. Native M1/M2/M3 support. Slick UI with a genuinely useful dashboard. Rosetta support for running x86 images on ARM. Built-in Linux VM management (so you can drop into a Linux shell without spinning up a full VM separately). Docker Compose support out of the box. Resource usage is dramatically better than Docker Desktop.

The bad: Not free for commercial use. Personal/hobby use is free; commercial use requires a subscription ($8/month or so, depending on plan). It’s also relatively new — battle-tested, yes, but Docker Desktop has a decade of edge case handling.

Installation:

brew install --cask orbstack
# Or download from orbstack.dev

OrbStack integrates seamlessly with the Docker CLI:

# Just use docker normally — OrbStack intercepts the socket
docker run --rm hello-world
docker compose up -d

RAM at idle: roughly 300-600MB. Startup: 3-5 seconds. Cost: free for personal use, paid for commercial.

The Comparison Table

Benchmark Reality Check

Tested on an M2 MacBook Pro (16GB RAM), running a docker compose up with a Node.js app + Postgres + Redis:

Docker Desktop:

• Cold start to ready: ~75 seconds (includes Desktop startup)
• Compose up time: ~18 seconds
• Memory used after compose up: ~4.8GB

Colima (4 CPU, 6GB allocated):

• Cold start to ready: ~32 seconds
• Compose up time: ~20 seconds
• Memory used after compose up: ~2.1GB

OrbStack:

• Cold start to ready: ~8 seconds
• Compose up time: ~15 seconds
• Memory used after compose up: ~1.4GB

OrbStack wins the speed race convincingly. Colima wins the control-freak race. Docker Desktop wins the “my company pays for it and I can’t be bothered to change” race.

So Which One Should You Actually Use?

Use Docker Desktop if:

• You’re a beginner and want zero friction getting started
• Your company has a Docker Business subscription and IT handles it
• You actually use Kubernetes locally and want the built-in integration
• You like GUIs and dashboards more than terminal output

Use Colima if:

• You’re comfortable in the terminal and Linux environments
• You want maximum control over VM resources
• You’re using it on a work machine where you can’t justify subscription costs
• You want to run multiple isolated Docker environments simultaneously
• You’re on an older Intel Mac and performance headroom matters

Use OrbStack if:

• You’re on Apple Silicon and care about startup speed
• You want a Docker Desktop experience without the RAM tax
• You’re a solo dev or doing personal projects (it’s free for that)
• You want a slick UI but also full terminal access

The honest answer for most developers in 2026: try OrbStack first. If you hit the paywall and don’t want to pay, switch to Colima. Docker Desktop is rarely the right answer unless you’re in an enterprise environment where someone else is paying.

The Migration Path

Already on Docker Desktop and want to switch? It’s easier than you think:

# Quit Docker Desktop completely (whale icon → Quit Docker Desktop)

# Install your replacement
brew install --cask orbstack
# or
brew install colima docker docker-compose

# Your existing images are gone (they lived in Docker Desktop's VM)
# Pull them fresh or rebuild from Dockerfiles — you were doing that anyway, right?

# Verify Docker CLI works
docker ps
docker run --rm hello-world

Your docker-compose.yml files don’t need to change. Your Dockerfiles don’t change. The container runtime is different; everything above it stays the same.

The Bottom Line

Docker on Mac has always been an exercise in managed disappointment. You’re running Linux containers inside a VM on top of a Unix-adjacent OS, and the whole thing should feel clunky — but it mostly doesn’t, which is honestly impressive.

Docker Desktop gets credit for making this accessible to millions of developers who never thought about any of this. But “accessible” and “efficient” aren’t the same thing, and in 2026, you don’t have to choose between ease and performance the way you used to.

OrbStack has become the default recommendation for anyone on Apple Silicon who doesn’t want to think too hard about it. Colima remains the right answer for anyone who wants total control without a subscription. Docker Desktop survives on inertia and enterprise contracts.

Your Mac’s RAM is finite. Your patience is finite. Your soul has market value. Spend all three accordingly.