--network-address leads to error - connection to the server was refused

[nagybalazs89]

I have the following colima.yaml file:

vmType: vz # qemu
mountType: virtiofs # sshfs
network:
  address: true
runtime: containerd
kubernetes:
    enabled: true
    version: v1.25.5+k3s2 # tags from https://github.com/k3s-io/k3s/releases
    disable: # coredns local-storage metrics-server
        - servicelb
        - traefik

If I run colima start I got the following error:

INFO[0000] settings from older colima version detected and copied 
INFO[0000] starting colima                              
INFO[0000] runtime: containerd+k3s                      
INFO[0000] creating and starting ...                     context=vm
INFO[0034] provisioning ...                              context=containerd
INFO[0034] starting ...                                  context=containerd
INFO[0039] provisioning ...                              context=kubernetes
INFO[0039] downloading and installing ...                context=kubernetes
INFO[0061] loading oci images ...                        context=kubernetes
INFO[0066] starting ...                                  context=kubernetes
FATA[0089] error starting kubernetes: error running [lima kubectl cluster-info], output: "The connection to the server localhost:8080 was refused - did you specify the right host or port?", err: "exit status 1"

If I run kubectl get pods -A I got a similar error:

The connection to the server localhost:8080 was refused - did you specify the right host or port?

Same happens if I ssh into the vm (colima ssh then kubectl get pods -A).

Also, colima does not create a kubeconfig file (~/.kube/config does not exist) and if I ssh into the vm and run kubectl config view I see the default (empty) kubeconfig file:

apiVersion: v1
clusters: null
contexts: null
current-context: ""
kind: Config
preferences: {}
users: null

If I run colima delete I also got a warning:

INFO[0001] deleting colima                              
WARN[0001] error retrieving runtimes: error retrieving current runtime: empty value 
INFO[0001] done   

If I remove the

network:
   address: true

part from the colima.yaml file everything works fine (but in that case I do not have a reachable IP).

NOTE: same happens if I go with a very basic config, e.g.: colima start --kubernetes --network-address. If I go without k8s like colima start --network-address then there is no error but if I run colima list then the Address tab is empty.

OS: macOS Ventura (13.2), Colima version: 0.5.2

Do you guys have any idea why is this happening? I was debugging this all day but found nothing and was not able to solve it. Thanks!

EDIT: If I switch to arch: x86_64 it works, but the address is still empty and there is no col0 device:

PROFILE    STATUS     ARCH      CPUS    MEMORY    DISK      RUNTIME           ADDRESS
default    Running    x86_64    4       4GiB      100GiB    containerd+k3s    

[nagybalazs89]

I was able to fix it by

rm -rf ~/Library/Caches/colima
rm -rf ~/Library/Caches/lima
rm -rf /opt/colima

brew uninstall colima
brew uninstall lima

and then restarted my computer, and reinstalled colima.