FriendlyELEC-Forum

I am using the following:

rk3399-sd-friendlydesktop-bionic-4.4-arm64-20180921.img
Booting from a Samsung 32GB EVO Plus microSDHC
NanoPi M4 Heat Sink with added fan
NanoPi M4 4GB

I tried a fresh image and an updated/upgraded image
Ubuntu 18.04 LTS 4.4.143
SSH enabled and QT Enabled

The docker ce install instructions from
Get Docker CE for Ubuntu
https://docs.docker.com/install/linux/docker-ce/ubuntu/

I am receiving the following error
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2018-10-30 07:03:04 MST; 18ms ago
Docs: https://docs.docker.com
Process: 4989 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
Main PID: 4989 (code=exited, status=1/FAILURE)

Oct 30 07:03:04 NanoPi-M4-00 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Oct 30 07:03:04 NanoPi-M4-00 systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 30 07:03:04 NanoPi-M4-00 systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce:armhf (--configure):
installed docker-ce:armhf package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: /lib/arm-linux-gnueabihf/libqtqrcode.so.1 is not a symbolic link

Processing triggers for systemd (237-3ubuntu10.3) ...
Errors were encountered while processing:
docker-ce:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@NanoPi-M4-00:~$ sudo docker run hello-world
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

Any suggestions?

Default kernel doesn't have some of the right bits turned on.

I have an alternate config file I'm working on here:
https://github.com/ericvh/kernel-rockch ... _defconfig

Docker works, but still working on Kubernetes.

ericvh wrote:
Default kernel doesn't have some of the right bits turned on.

I have an alternate config file I'm working on here:
https://github.com/ericvh/kernel-rockch ... _defconfig

Docker works, but still working on Kubernetes.

Docker and Kubernetes should work with this one OOTB:
https://www.armbian.com/nanopi-m4/

Configs:
https://github.com/armbian/build/blob/m ... ig/kernel/
for this kernel:
https://github.com/armbian/build/blob/m ... ult.config

Thanks for the pointer to Armbian, at the very least its a much more "comfortable" environment than the default friendly setup -- particularly for kernel work. In any case, unfortunately I'm kinda stuck at the same spot -- docker works, kubeadm looks like everything is okay, but the master never goes Ready because coredns pods seems stuck in Pending mode:

coredns-576cbf47c7-25vrz 0/1 Pending 0 7m36s
coredns-576cbf47c7-skxc4 0/1 Pending 0 7m36s

I'm basically following Alex Ellis' blog on getting kube up on Raspbian, so there's probably some mismatches. Is there a better source for Armbian kubernetes howto (or better yet specific to RK3399 like NanoPc-T4 and NanoPi-M4 which are the cluster elements I'm going for)

Update -- I was going for Flannel because the blog said something about Weave not working on armhf so I was worried about more general Arm stability. However, installing weave unlocked coredns so now things seem to be working.

coredns wont start before you have installed (and fully working) pod network add-on.
See here : https://kubernetes.io/docs/setup/indepe ... od-network
On our system, you have only 2 options weavenet or flannel. The later will requiere vxlan kernel module.

and since flannel seems to be the source of my memory issues causing my rootfs corruption, I would recommand against it

ericvh wrote:
Thanks for the pointer to Armbian, at the very least its a much more "comfortable" environment than the default friendly setup -- particularly for kernel work. In any case, unfortunately I'm kinda stuck at the same spot -- docker works, kubeadm looks like everything is okay, but the master never goes Ready because coredns pods seems stuck in Pending mode:

coredns-576cbf47c7-25vrz 0/1 Pending 0 7m36s
coredns-576cbf47c7-skxc4 0/1 Pending 0 7m36s

I'm basically following Alex Ellis' blog on getting kube up on Raspbian, so there's probably some mismatches. Is there a better source for Armbian kubernetes howto (or better yet specific to RK3399 like NanoPc-T4 and NanoPi-M4 which are the cluster elements I'm going for) Love how PhenQ Works

Update -- I was going for Flannel because the blog said something about Weave not working on armhf so I was worried about more general Arm stability. However, installing weave unlocked coredns so now things seem to be working.

These are not the hypes which you can't describe even though because of that unlocked coredns