NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #73 by repository stars
Last release 6 days ago
02 Oct 2026
Release timing varies
gaps range from 2 weeks to 2 months
Rarely documented
notes for 10 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
211 releases · first in 2021
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is an hotfix release to address a regression for Kubernetes runtime.
This is an hotfix release to address a regression for Kubernetes runtime.
Full Changelog: v0.10.2...v0.10.3
This is an incremental stability release with bug fixes and features.
This is an incremental stability release with bug fixes and features.
--downloader flag to retain curl for downloads. Supports curl or native (default).colima stop --force no longer attempts to stop the container runtime before stopping VM.krunkit vm type.colima delete without --force) is now properly supported on Incus runtime, and container data would be auto-restored on recreation.COLIMA_CACHE_HOME environment variable. The cache directory stores the downloaded assets used by Colima.krunkit vm type.colima list for stopped instances.--force-disk-image flag in addition to --disk-image flag. The image must be a debian based distro with systemd. Note that this is for power users and not officially supported.NOTE: container runtime versions can be updated manually by running the colima update command.
v29.5.2v2.3.1v7.1Full Changelog: v0.10.1...v0.10.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is an incremental release with support for Docker Model Runner and improvements to the AI functionality introduced in v0.10.0 .
This is an incremental release with support for Docker Model Runner and improvements to the AI functionality introduced in v0.10.0.
Colima now supports Docker Model Runner as an AI model runner backend.
Docker Model Runner is now the default due to its simpler requirements. However, Ramalama can still be used.
# run a model (uses docker runner by default)
colima model run gemma3
# serve a model, chat interface available at localhost:8080
colima model serve gemma3
# explicitly specify the runner
colima model run gemma3 --runner docker
colima model run gemma3 --runner ramalama
# set the runner at start time
colima start --model-runner ramalamaThe runner can be configured via:
--runner flag on colima model commands--model-runner flag at colima startmodelRunner in the configuration fileDOCKER_CONFIG environment variable is now respected.Full Changelog: v0.10.0...v0.10.1
This release introduces AI support and other updates.
This release introduces AI support and other updates.
Colima now has AI support.
By leveraging Krunkit and Ramalama, Colima is able to provide the ideal platform to run confined, isolated and secure gpu-powered AI workloads on Apple Silicon devices.
# run a model
colima model run gemma3
# serve a model, chat interface would be availabe at localhost:8080
colima model serve gemma3
# for more
colima model --helpkrunkit virtual machine type with gpu support. colima start --vm-type krunkit.colima start --network-address.CONTAINERD_* and NERDCTL_* environment variables on the host.--port-forwarder=none to colima start.--mount=none to colima start.curl and shasum on the host.after-boot and ready provision modes for provision scripts.NOTE: container runtime versions can be updated manually by running the colima update command.
v29.2.0v2.2.1v6.21v1.35.0+k3s1.Full Changelog: v0.9.1...v0.10.0
Nothing published for this version
Nothing published for this version
This is a hotfix release to address disk error issues for a subset of users.
This is a hotfix release to address disk error issues for a subset of users.
Check v0.9.0 release notes for the main release notes.
Full Changelog: v0.9.0...v0.9.1
This is a new release with several fixes and new features.
This is a new release with several fixes and new features.
This has been a long requested feature and it is finally here. A new --network-mode flag has been introduced.
Valid options are shared and bridged with the default being shared.
colima start --network-address --network-mode bridged
⚠️ Bridged should only be used if required and the local network is compatible. Shared networking is still the recommended option and remains the default.
This applies only to newly created instances.
Colima now uses a separate virtual machine disk for container data as a means to guard against accidental loss of data.
A deleted instance would not delete the container data disk, and a subsequent colima start would attempt to reinstate the data.
Supported for Docker, Containerd and Incus runtimes. Kubernetes however is not yet support.
To delete all data, the --data flag should be passed to colima delete.
colima delete --data # delete instance and container data⚠️ While it works reliably, there are no guarantees against loss of data. It should be used as a disaster recovery mechanism.
--template=false to colima start.host.docker.internal has been improved and now works fine in Docker, Containerd and Kubernetes containers./tmp/colima has been removed as a default mount due to issues caused when Colima is being run by multiple users on macOS.ssh and grpc with the --port-forwarder flag. Defaults to ssh.--network-preferred-route flag to use the network address interface as the default route when network address is enabled. This resolves networking issue for some users.NOTE: container runtime versions can be updated manually by running the colima update command.
v28.4.0v2.1.4v6.16v1.33.4+k3s1 Full Changelog: v0.8.4...v0.9.0
Nothing published for this version
Nothing published for this version
This is another hotfix release to address a regression that causes exec /bin/sh: exec format error when running a cross-architecture image. The issue
This is another hotfix release to address a regression that causes exec /bin/sh: exec format error when running a cross-architecture image. The issue is finally resolved.
--template flag.--binfmt=false flag.Full Changelog: v0.8.3...v0.8.4
This is an hotfix release to address a regression that causes exec /bin/sh: exec format error when running a cross-architecture image.
This is an hotfix release to address a regression that causes exec /bin/sh: exec format error when running a cross-architecture image.
virtiofs when VZ is in use.colima status for all container runtimes.--k3s-arg flag.Full Changelog: v0.8.2...v0.8.3
Nothing published for this version
Nothing published for this version
Nothing published for this version
Rename --cpu flag to --cpus for colima start , to align with Lima. --cpu still works but deprecated.
This is an incremental release with bug fixes.
--binfmt flag and binfmt config. Defaults to true when Rosetta is disabled.--cpu flag to --cpus for colima start, to align with Lima. --cpu still works but deprecated.COLIMA_PROFILE environment variable. Resolves #1308.NOTE: container runtime versions can be updated manually by running the colima update command.
v28.3.3v2.1.3v6.14v1.33.3+k3s1 Full Changelog: v0.8.1...v0.8.2
This is an incremental release with bug fixes.
This is an incremental release with bug fixes.
VZ is now the default virtual machine type on macOS 13 or newer. Qemu can still be used if specified.--disk-image flag for colima start.Runtime version can be updated running the colima update command.
27.4.02.0.26.8Full Changelog: v0.8.0...v0.8.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →