Repository navigation
Question - How colima is different from using docker runtime and kubectl? #173
Replies: 3 comments 1 reply
|
Please put the question as the title, and elaborate in the post body. |
|
Hi, There are a number of gains with using Colima (vs Docker), here is one |
|
Colima vs Docker Desktop comes down to a few key differences: Under the hood:
Performance: # Enable VirtioFS for best mount performance
colima start --vm-type vz --vz-rosetta --mount-type virtiofsOn Apple Silicon with Rosetta 2 enabled ( Compatibility: # Point docker CLI at colima socket
export DOCKER_HOST="unix://${HOME}/.colima/default/docker.sock"
# Or symlink (what this discussion is about):
sudo ln -sf ~/.colima/default/docker.sock /var/run/docker.sockWhere Docker Desktop wins:
Where Colima wins:
For most dev workflows, Colima is a drop-in replacement. The main friction is no GUI — everything through |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi Folks,
I do have a question, but I am afraid it may look dumb... Forgive me anyway. This is a honest question and not a critic
I understand that colima can be used with several runtimes.
But assuming a docker runtime, what exactly am I gaining from using colima that I cannot do using only docker client and kubectl itself?
All reactions