Cannot build from an amd64 machine, needs to be arm64

[alexbarcelo]

I was trying to follow the Building instructions and on the make ... installer command I was getting an error related to the architecture of the imager docker image.

That was strange, and decided to try to run that from an ARM64 machine (I spinned up a VPS of AMD64 arch). Running that command from the VPS worked flawlessly.

There's probably some combination of flags that I was unable to find. If it is indeed trivial, maybe those flags could be added to the README.md. If it is not trivial, then maybe it is not worth it (it can wait for reaching a non-experimental build or whatever).

I wanted to leave this here just in case somebody else stumbles upon the same.

The exact error was:

make[3]: Leaving directory '.../talos-builder/checkouts/talos'
make[2]: Leaving directory '.../talos-builder/checkouts/talos'
make[2]: Entering directory '.../talos-builder/checkouts/talos'
v1.10.4-1-gc8811800c: Pulling from <username>/imager
no matching manifest for linux/amd64 in the manifest list entries
make[2]: *** [Makefile:454: image-installer] Error 1
make[2]: Leaving directory '.../talos-builder/checkouts/talos'
make[1]: *** [Makefile:476: installer] Error 2
make[1]: Leaving directory '.../talos-builder/checkouts/talos'
make: *** [Makefile:101: installer] Error 2

That was me trying to run the make REGISTRY=docker.io REGISTRY_USERNAME=<mydockerhubusername> installer from my desktop.

That said, the make ... kernel can be run from wherever (which is the slow part) and running this last line from a VPS costs peanuts and worked first try.

[samip5]

What might not be apparent is that if the kernel isn't built for both arches, providing an imager for both doesn't make sense either. Unfortunate, but true.

I think me and @pndrik both use an arm64 mac, so this is non issue there...

[pndrik]

Hi both,

Indeed, I'm using an ARM64 Mac as local build environment and we're using ARM64 runners in GitHub.

As I'm a bit tight on time and it does not stop us from maintaining the build, I'd look at it as a feature we can pick up later on.

@alexbarcelo If you've got some time at your disposal and you'd like to contribute that bit, please feel free (and encouraged) to send us a PR.