M2 Zero K3s installation

installation works well on an early release by @sinovoip

2020-04-28-ubuntu-16.04-server-bpi-m2z-sd-emmc.img

the quick install script on https://rancher.com/docs/k3s/latest/en/quick-start/ doesn’t run on a preferred 19.10 server image of mine by avaf. may be a kernel incompatibility on the k3s side. k3s does have support for ubuntu 16.04 and 18.04. @avaf could you link a recommend one of your 18.04 server images I could try/test?

Thanks

You could try this with the 19.10 image: Upgrade to LTS Try:

  • make sure you have enough free space (do some housekeeping)

     sudo apt-get clean all
     sudo apt-get purge $(dpkg -l | awk '/^rc/ { print $2 }')
    
  • update the system

    sudo apt-get update
    sudo dist-upgrade
    
  • edit the file /etc/update-manager/release-upgrades with jed:

    sudo jed /etc/update-manager/release-upgrades

# Default behavior for the release upgrader.

[DEFAULT]
# Default prompting behavior, valid options:
#
#  never  - Never check for, or allow upgrading to, a new release.
#  normal - Check to see if a new release is available.  If more than one new
#           release is found, the release upgrader will attempt to upgrade to
#           the supported release that immediately succeeds the
#           currently-running release.
#  lts    - Check to see if a new LTS release is available.  The upgrader
#           will attempt to upgrade to the first LTS release available after
#           the currently-running one.  Note that if this option is used and
#           the currently-running release is not itself an LTS release the
#           upgrader will assume prompt was meant to be normal.
**Prompt=lts**

and finally:

sudo do-release-upgrade

or check which LTS version it will upgrade, possibly 20.04 LTS:

sudo do-release-upgrade -c

it’s working better.

in Rasbian I’de have to add a cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1 in/boot/cmdline.txt is there a workaround?

Try this:

  • edit the file /boot/bpi-m2-zero_boot.cmd

  • add the parms to:

    setenv extra "no_console_suspend consoleblank=0 drm_leak_fbdev_smem=1 cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1"

  • recompile with:

    sudo mkimage -C none -A arm -T script -d bpi-m2-zero_boot.cmd bpi-m2-zero_boot.scr

Hi avaf as usual your input is always appreciated. Building kernels is beyond my know-how. This up side is that you’re Images seemed like the better ones to try the k3s install… and that last env requirement maybe be what is needed.