Yet there is a build for it => base-images/balena-base-images/python/raspberrypi4-64/alpine/3.13 at master · balena-io-library/base-images · GitHub
There is a
3.8.10-buster-build (balenalib/raspberrypi4-64-python:3.8.10-buster-build) → Docker Hub
python:3.8.10-buster-run → Docker Hub
Same when pulling from arch instead. Available:
Doesn’t appear to be any Python for aarch64 above 3.8.6 (Docker Hub).
Weird how some are being built and not others. Perhaps a build issue? It’s becoming quite a problem.
This has also stimulated a question. Why is %%BALENA_MACHINE_NAME%% suggested by default instead of %%BALENA_ARCH%%? It seems a pull of
raspberrypi4-64-alpine is roughly the same as `aarch64-alpine’ (except 40mb difference)? Except I would need to pull a different image for each aarch64 device types if I use the device name, but with the aarch I only need to pull one that works across multiple device types?
I see a few extra packages installed in the RPI4 image, what do we lose feature wise by using the Arch image instead (base-images/Dockerfile at master · balena-io-library/base-images · GitHub)?