colima
colima copied to clipboard
Container runtimes on macOS (and Linux) with minimal setup
### Describe the Issue Some domains return a `Parse error` on nslookup on the colima ssh server, this in turn ends up creating an NX domain on the guest. ```...
### Description I use macOS Monterey and try to use colima to replace docker Desktop. But sometime I can meet this two issue at same time no matter how whether...
in my m1 mac, even if I shut down all the Docker containers, I only opened the Colima service. The memory has not been released. ![image](https://user-images.githubusercontent.com/101607051/163776152-f986f7b2-18ba-4e1d-a55b-c90f447100ad.png) Now that the relevant...
Installing a chained CNI plugin seems to be ignored on v0.4.x. The CNI config gets set properly in `/var/lib/rancher/k3s/agent/etc/cni/net.d/` and the plugin executable gets installed properly in `/var/lib/rancher/k3s/data/current/bin/`, but it's...
### Description We are seeing an issue where colima will not restart after OS X shuts down if colima is running during shutdown. ```shell ➜ ~ colima start --verbose INFO[0000]...
### Description Running `colima start` on a fresh install fails with the following log: ``` INFO[0000] starting colima INFO[0000] runtime: docker INFO[0000] preparing network ... context=vm INFO[0000] creating and starting...
### Description Unable to create pods after starting due to: ``` Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 31s default-scheduler Successfully assigned kube-system/coredns-d76bd69b-ltgbb to...
### Description On my work mac I was trying Colima, and had to remove my old Docker Desktop socket and symlink Colima's socket - the issue & fix are documented...
### Description `colima` is unable to verify that the Kubernetes has started correctly when a `shared` or `bridged` network is used for the underlying VM. ### Version Colima Version: 0.4.4...
Improve the readability of the terminal output by increasing the color contrast for the vm startup
### Description Currently when the vm is started there is a "subsection" of terminal output aside the regular output prefixed with `INFO [0000]`. That subsection has a way too low...