--network-address leads to error - connection to the server was refused #623
Unanswered
nagybalazs89
asked this question in
Q&A
Replies: 1 comment
-
I was able to fix it by
and then restarted my computer, and reinstalled colima. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have the following
colima.yaml
file:If I run
colima start
I got the following error: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
thenkubectl 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:If I run
colima delete
I also got a warning:If I remove the
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 likecolima start --network-address
then there is no error but if I runcolima 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:Beta Was this translation helpful? Give feedback.
All reactions