Colima
Colima 0.10.3 is a command-line container environment for macOS and Linux that starts an isolated Linux virtual machine for Docker, containerd, Incus and optional Kubernetes.
What Colima provides
Colima uses a Lima virtual machine to provide a local Docker, containerd or Incus environment on macOS and Linux. It automates port forwarding, host-directory mounts and named instances, making it useful for local development and testing without changing the host into a full server installation.
Runtime and data boundaries
Docker mode still needs a Docker CLI, while containerd can be used with nerdctl and Kubernetes adds its own resource cost. Images, containers, volumes and cluster state live primarily inside the virtual machine; mounted host directories affect real files. Deleting an instance may remove its internal data, so export images and back up volumes first.
Version and architecture
Colima 0.10.3 supports macOS Intel or Apple Silicon and Linux x86_64 or aarch64. Default settings are suitable for a test instance, not a production capacity guarantee. Keep each instance's runtime, CPU, memory, disk, ports and mounts in a change record. Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Colima to this cloud drive
Baidu Netdisk
Save Colima to this cloud drive
Colima 0.10.3 installation and Docker/containerd quick start
Start a default test instance, verify the CLI context, ports and mounts, then create separate configurations for containerd or Kubernetes and back up data before deletion.
Before you start
- Use a macOS or Linux host with supported hardware virtualization and enough space for VM images, layers and volumes.
- Install Docker CLI for Docker mode, nerdctl for containerd or kubectl for Kubernetes, and check that old contexts are not masking the intended runtime.
- Record existing contexts, ports, mounts and project data; export databases and named volumes before changing an important instance.
Installation steps
- 01
Install the matching 0.10.3 binary
Select Intel or Apple Silicon for macOS and x86_64 or aarch64 for Linux, place the executable in a trusted command directory and verify its version.
- 02
Start a default Docker instance
Run the default start command, wait for the VM and runtime, then inspect status and Docker information to confirm the context, architecture and daemon.
- 03
Tune an isolated configuration
Set CPU, memory, disk and mounts for a test project. Create a separate named instance for containerd, Incus or Kubernetes rather than changing a data-bearing instance in place.
Quick start
- 01
Run a disposable test container
Use a small public test image, inspect architecture, DNS and network behavior, then remove the container and image if it is not needed.
- 02
Verify ports and mounts
Start a test service with a port mapping and mount a dedicated directory, then check host access, permissions, read/write behavior and case sensitivity.
- 03
Test stop and restart
Stop the instance, confirm the service is unavailable, restart it and check that only intended containers and volumes remain; treat this as a persistence check, not a backup test.
Usage tips
- Kubernetes adds CPU, memory and disk pressure; use a separate instance when the cluster is experimental.
- Apple Silicon can run some x86_64 workloads through compatibility layers, but images and native dependencies may still differ.
- Keep Docker context and DOCKER_HOST visible in runbooks so commands do not reach the wrong daemon.
Troubleshooting and uninstall
Why does Docker still connect to another daemon?
Inspect the active Docker context and DOCKER_HOST, clear stale shell variables and select the Colima context after confirming the instance status.
Why are mounts slow or permission-denied?
Test a dedicated local directory, check host permissions and VM file-sharing settings, and avoid using a network or synchronized folder as the first benchmark.
- Export images, volumes and project dataStop writes, export required images, back up databases and named volumes, verify a restore and record the instance configuration before deletion.
- Delete the intended instance and binaryConfirm the exact profile name, remove that instance, then uninstall the executable and unused configuration only after the data review is complete.
Frequently asked questions
Does Colima include the Docker command-line client?
Colima supplies the virtual machine and runtime integration; Docker mode still requires Docker CLI, while containerd commonly uses nerdctl.
Does deleting an instance preserve its images, containers and volumes?
Do not assume they are preserved. Export images and back up named volumes and databases before deleting the exact instance profile.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.