fix(infra): correct OTel collector image tag
CI / commits (pull_request) Successful in 1m4s
CI / scan (pull_request) Successful in 1m12s
CI / check (pull_request) Successful in 1m13s
CI / a11y (pull_request) Successful in 44s
CI / perf (pull_request) Successful in 1m37s

`otel/opentelemetry-collector-contrib:0.115.0` does not exist on
Docker Hub — release 0.115 was published as `0.115.1` only (the
`.0` patch was either yanked or never built). Like the Jaeger
mistake in #58, I picked it from memory in #57 without
verification:

    Error response from daemon: failed to resolve reference
    "docker.io/otel/opentelemetry-collector-contrib:0.115.0":
    not found

Pin to `0.150.1`, the most recent stable patch. The collector
promises backward-compat for stable features (otlp receiver,
batch processor, debug exporter, otlp exporter), so our
`otel-collector.yaml` keeps working as-is. Renovate's
docker-compose manager will surface future bumps automatically.

Postgres / Redis / pgweb tags were verified against Docker Hub at
the same time; they are correct.
This commit is contained in:
Julien Gautier
2026-05-08 20:21:44 +02:00
parent f0372adaae
commit 8f892972dc
+1 -1
View File
@@ -80,7 +80,7 @@ services:
retries: 5 retries: 5
otel-collector: otel-collector:
image: otel/opentelemetry-collector-contrib:0.115.0 image: otel/opentelemetry-collector-contrib:0.150.1
container_name: apf-portal-otel-collector container_name: apf-portal-otel-collector
restart: unless-stopped restart: unless-stopped
command: ['--config=/etc/otel-collector.yaml'] command: ['--config=/etc/otel-collector.yaml']