This should, together with a PR I will create shortly on the main repo, allow us to build an arm64 version of the contributor image.
I did build it locally (which also uses qemu) and it builds. I can also run it (with qemu again) and the container starts up, builds everything, creates a chroot and starts all services. Submitting worked, but judging seems to hang. I'm thinking this is because of qemu. When I get my arm64 Mac (in ~2 weeks) I will test if it works there natively.
Note that building using qemu is a lot slower (for the arm64 image that is), but GItLab does not have native arm64 hardware, so it seems like the best approach for now.
Later we could also publish arm64 versions of the main images, but I'm not sure if that will be used in general. I hope no one is crazy enough to run domserver or judgehosts on an M1 Mac and other arm64 hardware is quite limited (there is AWS Graviton, but that's about it). Doing the main images also requires some more work, since we are building them in two steps.
This should, together with a PR I will create shortly on the main repo, allow us to build an arm64 version of the contributor image.
I did build it locally (which also uses qemu) and it builds. I can also run it (with qemu again) and the container starts up, builds everything, creates a chroot and starts all services. Submitting worked, but judging seems to hang. I'm thinking this is because of qemu. When I get my arm64 Mac (in ~2 weeks) I will test if it works there natively.
Note that building using qemu is a lot slower (for the arm64 image that is), but GItLab does not have native arm64 hardware, so it seems like the best approach for now.
Later we could also publish arm64 versions of the main images, but I'm not sure if that will be used in general. I hope no one is crazy enough to run domserver or judgehosts on an M1 Mac and other arm64 hardware is quite limited (there is AWS Graviton, but that's about it). Doing the main images also requires some more work, since we are building them in two steps.