ci(docker): Publish versioned, multiarch releases

[davidsow]

Which problem is this PR solving?

This change to the publication process solves two outstanding issues:

• Resolves Support ARM64 arch image #124
• Resolves Spark dependencies image is not tagged on dockerhub #64

As these two issues have been outstanding for some time, I opted not to create a new issue for these changes. I am happy to rectify that if need be.

Description of the changes

Versioned Publication

• The existing publish-image.yml GitHub workflow has been retooled to allow for tagged releases.
• The publication workflow now runs on two additional triggers:
  • release: Creating a release on the GitHub repo will publish an image with a matching tag
  • workflow-dispatch: The workflow can be run manually with an arbitrary tag string.
  • Both new triggers will also update the latest tag, preserving the current behavior.

This change presupposes no particular release / versioning strategy - it merely provides the foundation
for adopting one. At present, any deployment of this software is vulnerable to a breaking release of the
code overriding the latest tag with no warning. This change provides the ability to create a long-lived
image publication that can be considered stable.

ARM64

• The publish-image.yml workflow now publishes both linux/amd64 and linux/arm64 images.

Tests

• The version of testcontainers has been updated to v1.20.6 to fix a bug preventing tests passing on (at least) Apple M1 hardware.

How was this change tested?

• Executed testing instructions listed in README.md
• GitHub workflow behavior was tested on a private testbed repository to ensure correct dispatch behavior and tag computation.
• The linux/arm64 variant of the image builds and tests well on Apple M1 hardware.
  • Testing on other ARM-based chips remains outstanding.

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[yurishkuro]

Thanks for the fix!

[yurishkuro]

I think we should remove this trigger, otherwise latest is just random, not an official release

[davidsow]

I'm inclined to agree! I just retained it to preserve the existing behavior. I'll remove it in a followup commit shortly.

[yurishkuro]

Thanks!

[yurishkuro]

@davidsow https://github.com/jaegertracing/spark-dependencies/actions/runs/13777743816/job/38530254487

ERROR: Multi-platform build is not supported for the docker driver.
Switch to a different driver, or turn on the containerd image store, and try again.

[davidsow]

Interesting - I will run this down and determine a fix.

[yurishkuro]

you probably need buildx, see this example https://github.com/jaegertracing/docker-protobuf/blob/20742e70e824967ad7abd13e693238fc612bbfb2/.github/workflows/build-and-publish.yml#L24

[davidsow]

That does seem to be the problem! I've opened #154 to rectify the build failure