Cannot build two arch on two distinct jobs

[benoit74]

See openzim/zimit#538 (comment)

Currently, the action does not support building each arch image on a native runner and then publishing a manifest.

Note sure how we can support that in the future.

[rgaudin]

Nice to have but clearly just an optimization. Popular GH actions workflow have caught up the features they were lacking when we built this one. I feel it might be wiser to investigate/document/switch to a more standard (in a sense that we don't maintain) rather than investing any non-trivial time here.

[benoit74]

Could you develop why we've created this specific action in the first place? (what was missing in popular GH actions)

Nota: I've found https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners which is exactly what I intended to achieve for zimit

[rgaudin]

Could you develop why we've created this specific action in the first place? (what was missing in popular GH actions)

I think at this time what we wanted was:

• single github action for publishing images in CI (we were doing it manually before that) so it can be easily adopted by all repos.
• publishing to both docker hub and ghcr. I think that was the missing part.
• Flexible, human-friendly way to set tags for our workflow: tag on release, latest on master, etc. That would otherwise require additional steps.

Later we also adopted buildx with multi arch support before it was adopted in other actions.