Raspberry Pi 4 Support with upgrade to buster [FIXED] - Package Upgrades

[lucashalbert]

This PR piggy backs on PR #116 from @jmatsushita. It includes all of the fixes from that PR and updates the Docker Engine, Containerd, Docker Machine, and pi4 kernel.

[poupryc]

@lucashalbert Hi!
could you please output an image so I can test some features?
Thank for your work!

[lucashalbert]

@HelloEdit I just uploaded a pre-release here.

Let me know how it works for you.

[poupryc]

Thank @lucashalbert,

I just have a quick question: is it normal that the ssh and wifi headless configuration doesn't work? The system doesn't seem to take into account the presence of the ssh and wpa_supplicant.conf files at the root for the first boot.

EDIT: In fact it seems that I can't connect at all by configuring wlan0 from the raspberry (test done on a raspberry pi 3)

$ sudo iwlist wlan0 scan
    wlan0        Interface doesn't support scanning : Network is down
$ ifconfig -a
wlan0 ....

[lucashalbert]

@HelloEdit try running sudo ifconfig wlan0 up followed by sudo iwlist wlan0 scan.

[poupryc]

Thanks!
Still with your image @lucashalbert, docker is not launched nor working.

HypriotOS/arm64: pirate@black-pearl in ~
$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

HypriotOS/arm64: pirate@black-pearl in ~
$ systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-03-05 20:50:34 UTC; 16min ago
     Docs: https://docs.docker.com
  Process: 662 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 662 (code=exited, status=1/FAILURE)

[lucashalbert]

@HelloEdit It looks like the Raspberry Pi 3 doesn't like iptables-nft which is the default in Buster. For the time being, you will have update the link for the iptables command via alternatives to make it work.

Try running update-alternatives --set iptables /usr/sbin/iptables-legacy on your pi and then restart docker via systemctl restart docker.service.

What seems strange to me is that the new iptables-nft binary command worked without any issues on my Raspberry Pi 4.

[skj-dev]

FWIW, if you plan on using Buster as a Kubernetes node you need to set both iptables and ebtables alternatives to their -legacy implementations or kube-proxy won't work.

[aatchison]

I've been using k3s.io which uses containerd instet of docker I believe, with no issue.

…

On Thu, Mar 5, 2020, 4:06 PM Sean Johnson ***@***.***> wrote: FWIW, if you plan on using Buster as a Kubernetes node you need to set both iptables and ebtables alternatives to their -legacy implementations or kube-proxy won't work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#117?email_source=notifications&email_token=ACBE4O6US6UGYH5XAT47M6DRGA47ZA5CNFSM4K3IQ6ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN7K5BQ#issuecomment-595504774>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBE4OYSYPCBIGU6KIAOJ73RGA47ZANCNFSM4K3IQ6ZA> .

[lucashalbert]

I too, like @aatchison, have been using k3s on this image to run an 11 node HA kube cluster. K3s is much lighter than full k8s. The k3s binaries also seem to work without issue with nf_tables, so no need to change any of the iptables/ebtables links via alternatives.

[Shadester]

Does this contain the 64bit docker? Like so:

Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:26:27 2020
 OS/Arch:           linux/arm64
 Experimental:      false