I think the best workaround for now would be to use the specific image sha256 for the target architecture. For example:
netdata/netdata@sha256:b192922c4c1ecb3462326826d44d00d45e42703acaa57a935efedf555dbc32da
There is also the platform: field in docker-compose you could use.
I’m not 100% sure platform: will be respected by balena deploy but in the worst case you could run a compose build/pull first, then a balena deploy and it will happily push the images you already pulled/built.
docker-compose pull
balena deploy <app>
Either of these methods should work until we have worked out the required CLI change.