CI fails consistently due to trying to pull an unreleased Docker tag of camunda/zeebe (we're doing a release of that version in parallel just now):

Error: Run 1: RollingUpdateTest.shouldBeAbleToRestartContainerWithNewVersion(String, String)[2] ? Completion org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=camunda/zeebe:8.6.25, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@5b6f0bac)

I can only assume that the codes checks the GitHub tags and tries to infer that the Dockerhub tag should also exist - reaonable assumption but it has edge cases....

Edge case 😅

@cmur2 I don't see how your comments relate to this PR. What do you mean?

@cmur2 I don't see how your comments relate to this PR. What do you mean?

Sorry, I pasted the log of a failing CI run on this PR without the link: here you see the error before my retries (and before 8.6.25 was fully released): https://github.com/camunda/camunda/actions/runs/17206355916/job/48809373302

It relates insofar as that the timing of this PR exposed a flaw in the Zeebe QA - Update tests on the base branch.

@cmur2 Ah thanks for sharing the link. No I didn't see the failures before the retries. Sadly, GH doesn't show retries in a PR.