feat: build custom flavor image for linux/arm64#6988
Conversation
✅
|
…ty/megalinter into arm-custom-flavor-builder-image
|
@nvuillam fixed: https://github.com/oxsecurity/megalinter/actions/runs/21333862700/job/61402966050 Published image (you can see that it targets AMD and ARM): https://github.com/oxsecurity/megalinter/pkgs/container/megalinter-custom-flavor-builder/656247808?tag=alpha |
echoix
left a comment
There was a problem hiding this comment.
Looks fine, is everything fixed and ready now?
|
I tested with alpha branch, the docker build then merge into a single image seems to work :) https://github.com/oxsecurity/megalinter/actions/runs/21650936876/job/62415155448#step:7:1 @bdovaz @echoix if the result seems good to you, let's merge :) My only interrogation is about the parts in black below ("unknow/unknown" platforms) Name: ghcr.io/oxsecurity/megalinter-custom-flavor-builder:alpha Manifests: Name: ghcr.io/oxsecurity/megalinter-custom-flavor-builder:alpha@sha256:41038e3227c801ddd8d5606a616cc9ec4056c3a670b62a6f1adec7cfd734c326 Name: ghcr.io/oxsecurity/megalinter-custom-flavor-builder:alpha@sha256:6e6db3eaf43cf5e0d072cb0cd5dc90e97a9c559a86c33a0c987652703f8825fa Name: ghcr.io/oxsecurity/megalinter-custom-flavor-builder:alpha@sha256:2de629a305f3dddaf2ccc5bf21b12997d933c1d5cc4bcc274ca8e391d8938bd8
|
|
@nvuillam, if you're referring to the unknown/unknown issue, it's caused by https://github.com/docker/build-push-action/releases/tag/v4.0.0, as mentioned at docker/build-push-action#820 And the solution seems to be to disable that, do you agree? I don't know what it involves either, but I do know that there are a lot of references over the years to that PR issue from different repositories disabling it. cc @echoix |
|
let's have a leap of faith ! ;) (and it doesn't seem blocking) Merged ^^ |
I agree, it would be something to address after. But for the linked issue, I don't think removing the provenance is better, but maybe playing around with the platform could work around it. Because removing the provenance/attestation makes no sense if we are already working towards pinning everything, running trivy, and trying to have something SBOM-able |


If there are no typos and I haven't made any mistakes, this change should cause the image from megalinter-custom-flavor-builder to also be generated for
linux/arm64.This is the first step towards gradually generating the different images in this repository for
linux/arm64.I based it on the official example: https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners
Which I tested myself in:
https://github.com/bdovaz/docker-multi-platform/blob/main/.github/workflows/docker.yml
https://github.com/bdovaz/docker-multi-platform/pkgs/container/docker-multi-platform