Colima v0.9.0

v0.9.0macOSLinux
Added 5
  • Add --network-mode flag to support bridged and shared networking modes, with shared as the default
  • Add persistent disk feature for container data that survives instance deletion for Docker, Containerd, and Incus runtimes
  • Add --data flag to colima delete command to delete both instance and container data
  • Add --port-forwarder flag to make port forwarder configurable between ssh and grpc, defaulting to ssh
  • Add --network-preferred-route flag to use the network address interface as the default route when network address is enabled
Changed 4
  • Update Docker version to v28.4.0
  • Update Nerdctl version to v2.1.4
  • Update Incus version to v6.16
  • Update K3s version default to v1.33.4+k3s1
Fixed 4
  • Reinstate previous template loading behavior where Colima loads config from template file if present, with ability to disable via --template=false
  • Improve DNS resolution for host.docker.internal to work correctly in Docker, Containerd, and Kubernetes containers
  • Fix 386 architecture emulation when Rosetta is enabled
  • Sync default storage pool size for Incus runtime on startup to align with available disk space on the virtual machine
Removed 1
  • Remove /tmp/colima as a default mount due to issues when Colima is run by multiple users on macOS
Highlights

This is a new release with several fixes and new features.

New Features
Bridged network

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.

Persistent Disk

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.

Fixes
  • The previous behaviour with templates has been reinstated. i.e. Colima would load config from template file if present. It can still be disabled by passing --template=false to colima start.
  • DNS resolution for 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.
  • Port forwarder is now configurable between ssh and grpc with the --port-forwarder flag. Defaults to ssh.
  • Fix for 386 architecture emulation when Rosetta is enabled.
  • Introduction of --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.
  • The size of the default storage pool for Incus runtime is now synced on startup to align with the available disk space on the virtual machine.
Runtime version bumps

NOTE: container runtime versions can be updated manually by running the colima update command.

  • Docker version updated to v28.4.0
  • Nerdctl version updated to v2.1.4
  • Incus version updated to v6.16
  • K3s version defaults to v1.33.4+k3s1
Commits
New Contributors

Full Changelog: https://github.com/abiosoft/colima/compare/v0.8.4...v0.9.0

View original

Upgraded? How did it go?

Discussion