k3s not running on Raspberry Pi 3B about picl-k3os-image-generator

[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!