Trouble creating k3s cluster via rancher 2.6.3 on a rockPro64

Hello all,

I’ve created 2 nodes with both etcd and control plane on Red Hat 8.5 VMs and I am trying to create worker nodes on RockPro64s.

Rancher version 2.6.3
Rockpro64 - Armbian 21.08.1 Buster with Linux 5.10.63-rockchip64 and have also tried on:
RockPro64 - Ubuntu 20.04.3 LTS with Linux 5.10.63-rockchip64

Here is the command that I am running that rancher gives me:
curl -fL | sudo sh -s - --server --label '' --token qncvtblsx5bgfns828wnr79bhmzwsxq67ggh4gkwr5tr7j9jrhwm2z --worker

However I’m not getting much in the logs to help out, it just seg faults with this in the logs:

Here is the output of systemctl status rancher-system-agent

systemctl status rancher-system-agent.service

● rancher-system-agent.service - Rancher System Agent
     Loaded: loaded (/etc/systemd/system/rancher-system-agent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: signal) since Mon 2022-02-07 09:22:21 MST; 2s ago
    Process: 22956 ExecStart=/usr/local/bin/rancher-system-agent (code=killed, signal=SEGV)
   Main PID: 22956 (code=killed, signal=SEGV)

and I just get these in the logs:

-- The job identifier is 3874.
Feb 07 09:23:34 prtc-k3s-worker-b systemd[1]: rancher-system-agent.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support:
-- An ExecStart= process belonging to unit rancher-system-agent.service has exited.
-- The process' exit code is 'killed' and its exit status is 11.
Feb 07 09:23:34 prtc-k3s-worker-b systemd[1]: rancher-system-agent.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support:
-- The unit rancher-system-agent.service has entered the 'failed' state with result 'signal'.

I’ve searched the net and can’t find anything that I might be doing wrong.