Colima provides container runtimes on macOS and Linux.
While it is regarded as an alternative to Docker Desktop, Colima supports multiple container runtimes including Docker, Containerd, Kubernetes and Incus.
Some history
Colima started out as a personal bash script for running Docker and Kubernetes containers without needing Docker Desktop.
It builds on a project called Lima. The initial name was in fact, LimaKube before deciding on Colima two days later.
Due to positive feedback, it was later re-written in Go to add more capabilities. Nonetheless, it was meant to be just another toolkit for my use.
Surprising Popularity
Github issues kept piling and community engagements are on the rise. They however do not mean much, until I saw a notification in a WhatsApp group (of me and some of my friends) that reads as follows.
We’re leaving Docker Desktop at my office to use your work Colima
That opened the floor for conversations and it turned out some of my friends are already aware but waiting for the right moment to mention it to me. A while later another friend posted the following message.
We’ve been told to switch to Colima before end of month
I cannot help but wonder how a project without any documentation (asides the offical readme), is getting this much adoption.
There are many articles written and many videos made about Colima. However, this is the first time I would personally write about the project. I guess I must’ve done something right, for once.
Colima would go on to see contributions from 90 people and amass 24k stars on Github. It also sees thousands of downloads monthly on HomeBrew.
My toy, their tool
I have a personal saying that goes like this.
You can guage your project’s usefulness by pushing out a breaking change.
It was something I learned in the early days of Caddy as the maintainer of the docker image for Caddy v1.
I assumed that the docker image is barely used by others and knowingly mutated some tags, even though tags are meant to be immutable, ideally.
While Colima is a personal toy for my workflows, it is a tool relied upon by many with verying level of use-cases, like this one.
I do get reminded of Colima’s relevance anytime something goes wrong. Apart from Github issues, I do get contacted in all possible communication channels I have. 1
Github Secure Open Source Program
Colima was nominated and selected for the Github Secure Open Source Fund, a testament to it’s relevance.
Over the past few weeks, I attended days of workshops and trainings with focus on security for open source projects.
I had the honour of e-meeting maintainers of very popular open source projects including ExpressJS, Oh-My-Zsh, Flux CD, JUnit, Bootstrap, NativeScript and NVM. I also met multiple open source leaders, as well as security leaders at Github and Microsoft.
You can learn more about the Github Secure Open Source Program here.
What is next?
The current focus of the Colima project is to improve it’s stability, attend to security and bug fixes, and reliability related issues.
With the launch of Apple Containers and Lima gaining Windows support (via WSL2), there is more in store for Colima in the coming months.
Supporting the project
You can support Colima in multiple ways.
- Using Colima and providing valuable feedback.
- Engaging other users in communication channels (Github issues, Slack).
- Source code contribution
- Financial support on Github Sponsors, Buy Me a Coffee and Patreon.
-
I do not honour messages outside of the designated communication channels for the project. ↩︎