transport: authentication handshake failed: read tcp 127.0.0.1:59307->127.0.0.1:59306: read: connection reset by peer
dirien opened this issue · 3 comments
dirien commented
Hi,
I installed kim builder on an k3s node
➜ bin git:(main) ./kim builder install --selector k3s.io/build=my-builder-node --force
INFO[0000] Applying node-role `builder` to `stackit-containerd-ubuntu`
INFO[0000] Asserting namespace `kube-image`
INFO[0000] Asserting TLS secrets
INFO[0001] Asserting service/endpoints
INFO[0001] Installing builder daemon
INFO[0001] Waiting on builder daemon availability...
INFO[0008] Waiting on builder daemon availability...
INFO[0013] Waiting on builder daemon availability...
INFO[0019] Waiting on builder daemon availability...
```
The pod is running fine:
```
➜ bin git:(main) k get po -n kube-image
NAME READY STATUS RESTARTS AGE
builder-gl7nv 2/2 Running 0 6m2s
```
But if i try to build an image i get following message:
```
➜ bin git:(main) ./kim build --tag dirien/busybox .
[+] Building 0.0s (0/0)
Error: failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: read tcp 127.0.0.1:59307->127.0.0.1:59306: read: connection reset by peer"
Usage:
kim build [OPTIONS] PATH
Aliases:
build, image build
Any hints?
dweomer commented
The connection reset speaks to a crash of the backend service. Can you share the logs for 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
Additionally which architecture are you running on bloth client and server?
dirien commented
➜ 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.1.10.171:1234: i/o timeout"
Usage:
kim build [OPTIONS] PATH
Aliases:
build, image build
Logs:
➜ ~ k get nodes
NAME STATUS ROLES AGE VERSION
stackit-containerd-ubuntu Ready builder,control-plane,master 19m v1.20.6+k3s1
~ kubectl -n kube-image logs ds/builder -c buildkit
time="2021-05-19T06:59:57Z" level=warning msg="using host network as the default"
time="2021-05-19T06:59:57Z" level=info msg="found worker \"sc8350l4a127adn2qw3m1edto\", labels=map[org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:stackit-containerd-ubuntu org.mobyproject.buildkit.worker.snapshotter:overlayfs], platforms=[linux/amd64 linux/386]"
time="2021-05-19T06:59:57Z" level=info msg="found 1 workers, default=\"sc8350l4a127adn2qw3m1edto\""
time="2021-05-19T06:59:57Z" level=warning msg="currently, only the default worker can be used."
time="2021-05-19T06:59:57Z" level=warning msg="TLS is disabled for unix:///run/buildkit/buildkitd.sock"
time="2021-05-19T06:59:57Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
time="2021-05-19T06:59:57Z" level=info msg="running server on [::]:1234"
~ kubectl -n kube-image logs ds/builder -c agent
➜ ~