Container runtimes on macOS (and Linux) with minimal setup
This is a security release to address the following CVEs.
containerd.io package.colima ssh -- sh -c "sudo apt update && sudo apt install -y containerd.io"
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.7...v0.6.8
This is an incremental release to fix startup issues in v0.6.x.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
colima start would no longer download additional packages and should startup much faster. Fixes #900, #898, #896, #888, #880, #871, #868.vz vm type for M3 devices.Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.6...v0.6.7
This is an incremental release to fix host-gateway for Docker and redundant re-download of cached packages after running colima prune.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.5...v0.6.6
This is an incremental release to fix broken cli output introduced in v0.6.4.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.4...v0.6.5
This is an incremental release with bug fixes.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.3...v0.6.4
This is an incremental release with bug fixes and a new colima prune command to clear cached download assets.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.2...v0.6.3
This is a quickfix release to revert the host gateway IP address to 192.168.5.2 for communicating with the host from docker/containerd containers.
This is due to the fact that 192.168.5.2 has been the gateway address from the onset with many users having it hardcoded.
Note that host.docker.internal can also be used as an alternative within containers.
For more details about v0.6.0 features, check v0.6.0 release release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.1...v0.6.2
This is a quickfix release to handle regression with regards to hostname for virtual machines.
Check v0.6.0 release for the detailed release notes.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
Full Changelog: https://github.com/abiosoft/colima/compare/v0.6.0...v0.6.1
This release adds support for cgroup v2 and attempts to address some networking issues.
Due to breaking changes, deletion of existing profiles is required via colima delete.
Existing containers, images and volumes would be lost after upgrade.
$LIMA_HOME is still used if set.--layer flag. The underlying distro is now Ubuntu out of the box.--network-driver flag and using the new Lima user-v2 network. user-v2 has been more stable and should resolve most connectivity and DNS issues. However, --network-address is still supported.--hostname flag and hostname config to set custom hostname for the virtual machine.HTTP_PROXY, HTTPS_PROXY, NO_PROXY and their lowercase variants are now forwarded to the Docker daemon.user-v2 network. Fixes #648, #603, #577, #779, #137, #740.~ is used. Fixes #849.len check by @Juneezee in https://github.com/abiosoft/colima/pull/828
Full Changelog: https://github.com/abiosoft/colima/compare/v0.5.6...v0.6.0
This is a stop-gap release to addresses some stability issues.
--foreground flag for colima start to run Colima in foreground--cgroups-v2 flag for colima start as a temporary workaround for #764, a proper fix is in the works.Full Changelog: https://github.com/abiosoft/colima/compare/v0.5.5...v0.5.6