nestybox / nestybox/sysbox

Can not install Sysbox into K0s cluster (Kubelet binary not identified.)

Open
#606 5 comments 1 reaction 1 assignee View on GitHub

@rodnymolina is already working on this.

Since Nov 14, 2022.

enhancement
Dominant language
Shell
Stars
3.9k
Forks
230
Avg merge
7h 48m
Merged PRs (30d)
3

Description

Hello 👋 I have a K0s cluster (v1.23.13+k0s) that I want to install Sysbox into, but unfortunately the installation fails.

$ kubectl logs -n kube-system sysbox-deploy-k8s-mnm9h
Detected Kubernetes version v1.23
Deploying Kubelet config agent on the host ...
Running Kubelet config agent on the host (will restart Kubelet and temporary bring down all pods on this node for ~1 min) ...
Job for kubelet-config-helper.service failed because the control process exited with error code. See "systemctl status kubelet-config-helper.service" and "journalctl -xe" for details.

I find the error in the kubelet-config-helper logs:

$ sudo journalctl -eu kubelet-config-helper
...
Nov 13 23:26:22 my-host sh[2889612]: Detected systemd-managed host-based kubelet deployment on host.
Nov 13 23:26:22 my-host sh[2889655]: ++ get_kubelet_bin
Nov 13 23:26:22 my-host sh[2889657]: +++ systemctl show kubelet
Nov 13 23:26:22 my-host sh[2889658]: +++ grep ExecStart=
Nov 13 23:26:22 my-host sh[2889659]: +++ cut -d ';' -f1
Nov 13 23:26:22 my-host sh[2889655]: ++ local tmp=
Nov 13 23:26:22 my-host sh[2889655]: ++ tmp=
Nov 13 23:26:22 my-host sh[2889660]: ++ echo ''
Nov 13 23:26:22 my-host sh[2889661]: ++ xargs
Nov 13 23:26:22 my-host sh[2889612]: + kubelet_bin=
Nov 13 23:26:22 my-host sh[2889612]: + '[' -z '' ']'
Nov 13 23:26:22 my-host sh[2889612]: + die 'Kubelet binary not identified.'
Nov 13 23:26:22 my-host sh[2889612]: + msg='Kubelet binary not identified.'
Nov 13 23:26:22 my-host sh[2889612]: + echo 'ERROR: Kubelet binary not identified.'
Nov 13 23:26:22 my-host sh[2889612]: ERROR: Kubelet binary not identified.
Nov 13 23:26:22 my-host sh[2889612]: + exit 1
Nov 13 23:26:22 my-host systemd[1]: kubelet-config-helper.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 23:26:22 my-host systemd[1]: kubelet-config-helper.service: Failed with result 'exit-code'.
Nov 13 23:26:22 my-host systemd[1]: Failed to start Kubelet config service.

It appears that this helper script is unable to determine the correct Kubelet path. I first tried to symlink /usr/bin/kubelet -> /var/lib/k0s/bin/kubelet until I realized this is actually trying to obtain the Kubelet path from systemctl.

However, the Kubelet path is not to be found in systemctl show kubelet (kubelet.zip).

Is there a config option I can use to explicitly point the Sysbox installer to the right Kubelet binary?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.