Build AWS BalenaOS Image for ARM

Product support
1

Hi,

In the past I’ve used the pre-published balena images to launch devices on AWS. Since these are not available anymore I followed this post to create an Generic x86_64 image

Some of our devices run aarch64 - how can I build an arm image? I guess a need a specific link for bh.cr/balena_os/…. to do that?

thx,

Robert

2

Hi @RobertBakker ,

You can build a generic aarch64 image with yocto using this repo and specifically machine.

However I suppose you want to download a pre-built image.

You can do so in the way explained in the article you mentioned:

balena os download generic-aarch64 -o balena.img --version v6.12.3+rev2

Please keep us posted on how that goes for you.

Regards,

Yann

3

Hi @ycardaillac ,

Thanks for th quick response,. The page refers to

docker pull bh.cr/balena_os/cloud-config-amd64/461031537d2655560b9bc29ea2e1405c

I guess that should be something else for an arm build?

regards,

Robert

4

hm… I did create the amd image, but I just found out that it just doesn’t boot…. there’s nothing to see on of the ways AWS exposed information (systemlogs/screenshot/serial console..)

Since I spend enough time on this for now I’ll use the workaround to boot the old images I still had and upgrade the balenaOS via de belana web interface …

let’s hope that will keep working in the future…

5

Hi @RobertBakker,

Oh yes sorry, I thought you referred to the OS image, well I think this container image:

docker pull bh.cr/balena_os/cloud-config-amd64/461031537d2655560b9bc29ea2e1405c

is only a pre-built version of GitHub - balena-os/cloud-config: balenaCloud application used to configure balenaOS from supported metadata services · GitHub so you can clone the repo and balena push it to your fleet. Instead of using the pre-built image with FROM in a Dockerfile.

Your workaround should keep working as well, but it would be better if you’d be able to provision directly with a up to date OS image.

Regards,

Yann