This message was deleted.
# rancher-desktopa
adamant-kite-43734
01/22/2024, 1:34 PMThis message was deleted.
w
wide-mechanic-33041
01/24/2024, 6:09 PMwhats the reason for minikube? running kube inside of kube?
a
able-translator-31337
01/25/2024, 12:26 PMGood question, what we are trying to do is to replace Docker Desktop and we already have some local testing setup working with minikube.
I guess the correct way of doing this would be to replace minikube with the k8s engine that Rancher Desktop already has, but that is going to that some time and we are in a bit of a rush at the moment.
able-translator-31337
01/25/2024, 12:33 PMAfter some investigation I found the port 53 is taken on macOS by a process that is started when Rancher Desktop starts. Weird thing is that if I shutdown RD the port is still in use, unlike what that page says that it should be released, and if I start Docker Desktop minikube works.
So it does not look like having that port busy on the host is causing this issue.
w
wide-mechanic-33041
01/25/2024, 12:46 PMwhat is the diff you are seeing between minikube and the k3s node that is in RD? minikube as its own networking config and even if you disable k3s in RD and just use containerd i think you will be battling the product. you may just want to look at lima by itself to create a VM for minikube and do it manually rather than RD as an all in one product. 53 is dns so for some reason a request from the VM is not getting relayed upstream https://lima-vm.io/docs/config/network/ may help you troubleshoot what might be rejecting those packets.
2 Views