https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
r
Do basic docker commands such as 
docker images
, 
docker run
etc work?
w
and given RD includes a kubernetes env via k3s why are you trying to add another one using kind?
h
I think I found a solution for this problem: Run at least one time:
Copy code
docker run --rm -it --name kind-control-plane --privileged kindest/node:v1.27.3
kill this:
Copy code
docker stop kind-control-plane
Then run:
Copy code
kind create cluster
Maybe the first command generate some files on the host that needed for kind works.
Double checked in another macbook and works. There are my configs:
Really there are a problem with kind with rancher-desktop. Now it cannot pull images images from docker registry.
Copy code
LAST SEEN   TYPE     REASON                    OBJECT                    MESSAGE
52s         Normal   Starting                  node/kind-control-plane   Starting kubelet.
52s         Normal   NodeAllocatableEnforced   node/kind-control-plane   Updated Node Allocatable limit across pods
52s         Normal   NodeHasSufficientMemory   node/kind-control-plane   Node kind-control-plane status is now: NodeHasSufficientMemory
52s         Normal   NodeHasNoDiskPressure     node/kind-control-plane   Node kind-control-plane status is now: NodeHasNoDiskPressure
52s         Normal   NodeHasSufficientPID      node/kind-control-plane   Node kind-control-plane status is now: NodeHasSufficientPID
38s         Normal   RegisteredNode            node/kind-control-plane   Node kind-control-plane event: Registered Node kind-control-plane in Controller
36s         Normal   Starting                  node/kind-control-plane
35s         Normal   NodeReady                 node/kind-control-plane   Node kind-control-plane status is now: NodeReady
20s         Normal   Scheduled                 pod/test                  Successfully assigned default/test to kind-control-plane
19s         Normal   Pulling                   pod/test                  Pulling image "ubuntu:22.04"
0s          Warning   Failed                    pod/test                  Failed to pull image "ubuntu:22.04": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/library/ubuntu:22.04|docker.io/library/ubuntu:22.04>": failed to resolve reference "<http://docker.io/library/ubuntu:22.04|docker.io/library/ubuntu:22.04>": failed to do request: Head "<https://registry-1.docker.io/v2/library/ubuntu/manifests/22.04>": dial tcp: lookup <http://registry-1.docker.io|registry-1.docker.io> on 192.168.5.2:53: read udp 172.18.0.2:40849->192.168.5.2:53: i/o timeout
0s          Warning   Failed                    pod/test                  Error: ErrImagePull
0s          Normal    BackOff                   pod/test                  Back-off pulling image "ubuntu:22.04"
0s          Warning   Failed                    pod/test                  Error: ImagePullBackOff
One way to avoid this for now it's load the images inside kind's containers.
Copy code
kind load docker-image ubuntu:22.04
b
I fixed it by downgrading kind from 0.22 to 0.19
r
@hundreds-application-47252 I have the same problem and only with rancher-desktop. I don’t have this problem using colima or lima. When I hop onto the kind-control-lane container I can’t 
apt-get update
, it just hangs.
w
remember that colima is just docker in a vm (assuming you didn't use --kubernetes) using limavm. and limavm is just a vm. rancher by default orchestrates kubernetes for you so not 100% why you would use kind with RD vs just the built in k3s distribution, but guessing that is the issue you are running into.
r
Thanks. Was testing kind on RD since it was mentioned as being supported recently (https://github.com/rancher-sandbox/rancher-desktop/releases/tag/v1.13.0)
w
and thats fine so you disabled the RD K3s and are installing KIND and using that for K8s?
12 Views
Open in Slack
PreviousNext
Powered by