Closed plutoid closed 3 years ago
Getting the same issue with k3s-arm64 0.6.1 on armbian 5.88
with k3s v0.9.0-rc2 it seems to be fixed, according to upstream they backported it into k8s 1.15 :) I successfully was able to join a x86_64 k3s (running k8s 1.14) cluster from my rock64 arm64 running kernel 5.2.7 and spawn a busybox on it. have't done more testing yet.
Closing due to age.
Describe the bug when I start service with 'k3s start' on armbian, it complained with issue like that cannot open open /sys/fs/cgroup/hugetlb/kubepods/burstable/hugetlb.64kB.limit_in_bytes , but on OS filesystem the file /sys/fs/cgroup/hugetlb/kubepods/burstable/hugetlb.64KB.limit_in_bytes does exist, the difference is that file name including should be KB not kB, not sure which side is wrong here.
To Reproduce Steps to reproduce the behavior: start with: k3s server
Expected behavior hope check if this is issue on k3s or kubenetes
Screenshots
Additional context OS: armbian hardware: Amlogic S905D : image version: Linux aml 5.0.2-aml-s905 #5.77 SMP PREEMPT Mon Apr 1 17:41:33 MSK 2019 aarch64 GNU/Linux image file: image 5.77- s905: https://yadi.sk/d/pHxaRAs-tZiei
k3s version: K3s v0.5.0 /v0.5.0-rc4 ..
similar report on https://github.com/kubernetes/kubernetes/issues/77169