jbonofre opened a new issue, #748:
URL: https://github.com/apache/camel-karaf/issues/748
`camel-karaf-4.18.x` still pins the Pub/Sub emulator image tag that #745
found
had been pruned from `gcr.io`:
```java
DockerImageName.parse("gcr.io/google.com/cloudsdktool/google-cloud-cli:441.0.0-emulators")
```
#745 was fixed on `main` by #746 (bumped to `583.0.0-emulators`), but the fix
was never backported to the 4.18.x maintenance line.
### Why it matters now
`441.0.0-emulators` still resolved as recently as 2026-08-28 — the CI run for
PR #742 pulled it successfully (410 MB in the log). But `gcr.io` keeps only a
rolling window of the most recent emulator tags, so that pin has since
stopped
resolving.
The consequence is the one #746 described on `main`: Testcontainers fails the
container fetch with "manifest unknown", `CamelGooglePubsubITest` errors out
in
`initializationError`, and the Maven reactor halts at
`camel-google-pubsub-test`, skipping every later module.
This currently blocks meaningful CI on the 4.18.x line — including PR #742
(Upgrade to Camel 4.18.4), whose CI cannot be re-run and trusted until this
lands.
### Fix
Backport the `CamelGooglePubsubITest` change from #746 to
`camel-karaf-4.18.x`, including the comment recording the registry retention
behaviour so the next bump is not a mystery.
The other four pinned test images (cp-kafka, influxdb, localstack, rabbitmq)
are untouched, as in #746.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
