Closed adrianriobo closed 1 week ago
Here there is a sample on how we manage this on other project:
Makefile for build and aggreagate to manifest https://github.com/crc-org/ci-definitions/blob/71d9c0cc3371aec456fbb5c048cb8c6cd52c8e0a/Makefile#L66
Containerfile with target arch arg to manage the container assets arch properly https://github.com/crc-org/ci-definitions/blob/main/crc-builder/oci/Containerfile.linux#L4
Hey @lilyLuLiu I actually open an issue https://github.com/crc-org/ci-definitions/issues/32 as it seems this is not working as expected...mainly due to the strategy required for forked repos.
We basically create those images on the forked repo (as long as they are not tagged versions) then save as tar upload as artifacts and from the upstream context load and push to internal ghcr.
But it seems that save operation does not allow us to do the multiarch
To make the builded pusher strategy works there is a tricky thing needed to make in order to save images you can see https://github.com/crc-org/ci-definitions/pull/34/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R72
Closed by #318
Currently mapt and oci container is built only for x86 it should be built for multi-arch