Hello everyone!
Is Docker Desktop being detected as malware on macOS? If this has happened to you, join me in this post where I'll document the migration process to OrbStack, a tool that promises to be lighter and more efficient. This post will be updated with new findings as I continue using it.
How did this start?
On January 7th, 2025, reports began to emerge about malware detected on macOS (You can read more about it here). Docker Desktop started being reported as malware, affecting various users, including members of my team (M1, M2, and M3 users). Due to recent macOS updates, some didn't experience this issue, but it was eventually documented in the Docker forum.
In search of alternatives, we discovered OrbStack and decided to try it.
What is OrbStack?
OrbStack isn't just presented as an alternative to Docker Desktop, but as a more versatile solution, allowing you to run Linux in different environments, similar to what WSL offers on Windows.
Why Consider OrbStack?
While you can find a detailed comparison in the resources section, the key benefits that made me switch include:
Significantly lower resource usage (my MacBook's fans finally stopped spinning)
Faster container startup times
Better integration with Apple Silicon
A more modern and responsive interface
What is WSL?
While it's not the focus of this post, it's worth mentioning. For Windows users, Windows Subsystem for Linux (WSL) is an excellent alternative for using Linux tools within Windows.
Installing OrbStack on Mac
There are two main installation methods:
Using homebrew
brew install orbstack
Downloading the installer directly from orbstack.dev/download (make sure to select the correct installer for your processor)
Installation Process
Once installed, you'll follow these steps:
Welcome screen
Tool selection: we'll choose Docker (for now), but you can add K8s or Linux later
You'll see the following screen
To migrate existing Docker Desktop data:
The "Migrate Docker Data" option simplifies the transition, ensuring all your containers, images, and volumes are ready to use in OrbStack without data loss.
The migration process will take a few minutes depending on the amount of data
Docker Desktop will stop during the process
When everything is finished, we'll see all containers, volumes, and images successfully migrated
- Now, let's run a (test) project to confirm everything is working normally
First Impressions
I was able to run projects normally, without needing to change anything.
The interface is intuitive, and the migration process was quite smooth.
Although I've been using it for a short time, I've noticed that memory and CPU consumption is lower compared to Docker Desktop, especially when working with multiple containers.
Integration with existing development tools (VS Code, terminal) works quite well.
Technical Considerations
OrbStack's architecture differs from Docker Desktop in its virtualization approach, which explains the performance improvement. (See more at https://docs.orbstack.dev/architecture)
It's important to mention that environment variables and network configuration remain consistent after migration.
Volumes and bind mounts work similarly, maintaining compatibility with existing docker-compose files.
Useful Resources
Have you tried OrbStack or are you considering the switch? What do you think about this tool?
Share your experience in the comments, I'd love to learn from your findings!
Until the next post, let's keep coding and learning together!
