Fix issue with Buster base image and add support for arm64

[rahul-thakoor]

• replace libgnome-keyring with libsecret
• add dockerfile targeting arm64

Change-type: minor
Signed-off-by: Rahul Thakoor rahul@balena.io

[lurch]

Fixes #94 ?

[lurch]

According to https://www.balena.io/docs/reference/base-images/devicetypes/ raspberrypi3 is armv7hf, not aarch64 ?

[rahul-thakoor]

yes, we use the rpi3 base image for 32-bit support

[lurch]

So why is the rpi3 base image being used in Dockerfile.aarch64? Apologies if I'm not understanding something.

[imrehg]

@lurch because the 32-bit raspberrypi base image also has the raspbian repositories, so it's not directly the armv7hf base image. Here those might or might not be used, but for other device types, e.g. a Pi3, it would be a balenalib/raspberrypi3-node base image, and it's better to be on par, than one device type using the architecture base image, the other the device type bsae image (where they are not direcly the same)

[imrehg]

@rahul-thakoor maybe I would specify 10-buster-build here and in the other one, to ensure it's the right kind of debian, and less surprising.

Also, have you tried to build with 12-? If we could bump that it would be grand!

[lurch]

I still don't quite see why the "32-bit raspberrypi base image" is being used in the 64-bit Dockerfile.aarch64, but I'm not really that bothered so I won't bother hassling you any further 🙂

[rahul-thakoor]

@lurch there might be cases where 64bit packages or libraries are not available. so using 32-bit base image we can still make use of those on a 64bit system. Perhaps the following 2 PRs might be helpful to understand:

1. https://github.com/balena-io-playground/balena-senseoflife/pull/2/files
2. Add support for Pi3/4 64-bit images by using packages from Alpine balena-senseoflife#3

[lurch]

Oh, so even though the filename says Dockerfile.aarch64, the actual built image is actually all 32-bit code?

[rahul-thakoor]

Yes, Dockerfile.aarch64 targets 64bit systems and on those, we explicitly use 32-bit images otherwise they would default to the 64-bit ones

[rahul-thakoor]

@imrehg I pinned the based image to buster and use node-12
Tested on pi4(64bit balenaOS) and pi3 model b

[Ciantic]

@rahul-thakoor how did you make it to work with pi4? Did you use the Dockerfile.aarch64?

To me it seems like it's targeting 32bit, it says FROM balenalib/raspberrypi3-node:12-buster-build as build

and now I started to build it all the packages are armhf.

[Ciantic]

But, sir! It works! Using armhf build and rpi4.

Maybe not ideal. Should test for raspberrypi4-64-node support too, it would be fantastic!

[smarthomeagentur]

Hi,
are there any news here for pi4? This would be a great combination with electron. I only get to build but x11 crashes with " (EE) no screens found(EE) "