I’m experiencing the same problem. I’ve been running my project on local-mode using balena push, and it’s been working great. Which makes sense as I’m building the images locally using the --emulate flag for the build.
I don’t understand why Balena Cloud can’t work with the official base images which all support the architecture I’m building for. In examples by @klutchell such as balena-pihole and balena-nginx-proxy-manager the Dockerfiles don’t call the Balena machina: balenalib/%%BALENA_MACHINE_NAME%% or a tag especific to arm, such as balenalib/armv7hf-debian.
What’s the catch with my project not building for the correct architecture? Do I need to pass a Dockerfile as build option on the docker-compose?