We have been using QEMU to generate our rollups docker image. Previously it was only generating the images using the Linux/amd64 architecture, and the times were reasonable, around 6 minutes without intermittent connectivity problems. Once we included the Linux/arm64, though, the timing for that generation alone is around 26 minutes, and we often see network connectivity problems (screenshot below) naturally followed by CI failure because it usually never recovers that connection. Therefore, we are looking for an alternative to solve that problem and avoid the workaround, that is, to rerun it š« .
āļø Solution
Initially, move from QEMU to depot.dev, which is specialised in building docker images. PS: funny enough, the example on the main page is showing how fast it is to build something on arm64
š Context
We have been using QEMU to generate our rollups docker image. Previously it was only generating the images using the Linux/amd64 architecture, and the times were reasonable, around 6 minutes without intermittent connectivity problems. Once we included the Linux/arm64, though, the timing for that generation alone is around 26 minutes, and we often see network connectivity problems (screenshot below) naturally followed by CI failure because it usually never recovers that connection. Therefore, we are looking for an alternative to solve that problem and avoid the workaround, that is, to rerun it š« .
āļø Solution
Initially, move from QEMU to depot.dev, which is specialised in building docker images. PS: funny enough, the example on the main page is showing how fast it is to build something on arm64
Reference: Sunodo CLI Action
š Subtasks
DEPOT_PROJECT
for rollups-explorer on depot.dev.DEPOT_PROJECT
in the repository vars config to be available to the GitHub action.id-token: write
to be able to requestJWT
token.depot.dev
šÆ Definition of Done
rollups-explorer
images are published to the GitHub Registry a.k.a packages.