Error while dialing dial tcp 10.0.10.36:1234: i/o timeout

[dirien]

Hi,

i tried to build with kim an image on our RKE cluster.

Installing kim builder was successfull and the pod is running.

./kim builder install --selector k3s.io/hostname=my-builder-node --containerd-socket=/run/containerd/containerd.sock

When i try to run a build i get following error:

 ./kim build --tag dirien/busybox .  
[+] Building 0.0s (0/0)                                                                                                                                                                          
Error: failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.0.10.36:1234: i/o timeout"
Usage:
  kim build [OPTIONS] PATH

Aliases:
  build, image build

And i can not figure out, what the problem could be... Any hints from your side?

Thanks a lot.

[dweomer]

Please share the logs from the buildkit and agent containers in the pod:

• kubectl -n kube-image logs ds/builder -c buildkit
• kubectl -n kube-image logs ds/builder -c agent

[dirien]

What i found strange is, that KIM is using the internal IP adress of the worker node... Do i need to have access to the worker node from my local machine? I found this strange..

➜  bin git:(main) ./kim build --tag dirien/busybox . 
[+] Building 0.0s (0/0)                                                                                                                                                                          
Error: failed to dial gRPC: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.0.10.36:1234: i/o timeout"

➜  ~ kubectl -n kube-image logs ds/builder -c buildkit
time="2021-05-14T08:16:30Z" level=warning msg="using host network as the default"
time="2021-05-14T08:16:30Z" level=info msg="found worker \"me2vtk6tussd654e72009nfnr\", labels=map[org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:host-10-0-10-36 org.mobyproject.buildkit.worker.snapshotter:overlayfs], platforms=[linux/amd64 linux/386]"
time="2021-05-14T08:16:30Z" level=info msg="found 1 workers, default=\"me2vtk6tussd654e72009nfnr\""
time="2021-05-14T08:16:30Z" level=warning msg="currently, only the default worker can be used."
time="2021-05-14T08:16:30Z" level=warning msg="TLS is disabled for unix:///run/buildkit/buildkitd.sock"
time="2021-05-14T08:16:30Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
time="2021-05-14T08:16:30Z" level=info msg="running server on [::]:1234"
~ kubectl -n kube-image logs ds/builder -c agent
➜  ~

[dweomer]

Do i need to have access to the worker node from my local machine?

yes, unless you setup an ingress route.

[dirien]

How to i configure kim with an ingress route? Do you have an example? An simple kube-forward is not enough?

[dweomer]

How to i configure kim with an ingress route? Do you have an example? An simple kube-forward is not enough?

Apologies for the months-late response, forwards to the service endpoints should be fine.

[KevinOrtman]

I've run into this issue as well. I'm very new to kubernetes, and I'm not able to get a forward to work. Should this work?

kubectl port-forward svc/builder 1234:1234 --namespace kube-image

[dirien]

I will close this, as with rancher desktop its working fine.