k3s not running on Raspberry Pi 3B

[OmegaRogue]

i tried installing k3os with an image generated with the image generator on my raspberrypi 3, and k3s didnt start, I got this from running k3s check-config:

Verifying binaries in /home/rancher/.rancher/k3s/data/923c8cc79c27e6cc2f224ae559273abdd7024ad2b27c44ad00d002988331ca5f/bin:
- sha256sum: good
- links: good

System:
- /usr/sbin iptables v1.8.3 (legacy): ok
- swap: disabled
- routes: ok

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000

info: reading kernel config from /proc/config.gz ...

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled (as module)
- CONFIG_NF_NAT_IPV4: missing (fail)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module)
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_NF_NAT_NEEDED: missing (fail)
- CONFIG_POSIX_MQUEUE: enabled

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: missing
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: missing
- CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module)
- CONFIG_IP_SET: enabled (as module)
- CONFIG_IP_VS: enabled (as module)
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_PROTO_TCP: enabled
- CONFIG_IP_VS_PROTO_UDP: enabled
- CONFIG_IP_VS_RR: enabled (as module)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: enabled (as module)
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled (as module)
      - CONFIG_CRYPTO_GCM: enabled (as module)
      - CONFIG_CRYPTO_SEQIV: enabled (as module)
      - CONFIG_CRYPTO_GHASH: enabled (as module)
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled
      - CONFIG_XFRM_ALGO: enabled
      - CONFIG_INET_ESP: enabled (as module)
      - CONFIG_INET_XFRM_MODE_TRANSPORT: missing
- Storage Drivers:
  - "overlay":
    - CONFIG_OVERLAY_FS: enabled (as module)

STATUS: 2 (fail)

[coldfire84]

Had the same issue on a pi4 I recently tested k3os image on using instructions here https://www.chriswoolum.dev/k3s-cluster-on-raspberry-pi, it was down to date/ time being out of sync (ntp hadn't worked on boot).

My config/ yaml formatting ended up slightly different to the linked article, and it works now:

# the hostname you want to use for the Pi
hostname: k3os1

# a public key if you intend to use ssh to connect to the node. This is highly recommended since k3OS has no root user.
ssh_authorized_keys:
  - <redacted>

# Ethernet config
write_files:
- encoding: ""
  path: /var/lib/connman/default.config
  content: |-
    [service_eth0]
    Type=ethernet
    IPv4=192.168.1.10/255.255.255.0/192.168.1.1
    IPv6=off
    Nameservers=192.168.1.1

# Ensure NFS provider can start, will generate error otherwise: "Failed to stat /var/lib/nfs/sm: No such file or directory"
run_cmd:
- "mkdir -p /var/lib/nfs/sm"

# Enable rpsbind/ nfs services: https://github.com/rancher/k3os/issues/555 | https://github.com/democratic-csi/charts/issues/3
boot_cmd:
- rc-update add rpc.statd
- rc-update add nfs

k3os:
  ntp_servers:
  - 0.uk.pool.ntp.org
  - 1.uk.pool.ntp.org

  dns_nameservers:
  - 192.168.1.254

  k3s_args:
  - server

[frudolph77]

I've the very same problem, the solution form @coldfire84 does not work for me.

My network only uses DHCP and WIFI, so no fixed IPs. Therefore I had no connman config but I tried it also with a config.

I think the main problem is that busybox does not start the ntpd. When starting ntpd by hand and restarting k3s-service it is running fine.

Unfortunately I didn't get ntpd working on boot.

[sgielen]

Closing all issues, because the project is archived. Thank you for being a contributor and/or user!