From 8f892972dcfb6a25e785e615229c721e77ae3036 Mon Sep 17 00:00:00 2001 From: Julien Gautier Date: Fri, 8 May 2026 20:21:44 +0200 Subject: [PATCH] fix(infra): correct OTel collector image tag MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `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. --- infra/local/dev.compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infra/local/dev.compose.yml b/infra/local/dev.compose.yml index b16a5d1..8e0f841 100644 --- a/infra/local/dev.compose.yml +++ b/infra/local/dev.compose.yml @@ -80,7 +80,7 @@ services: retries: 5 otel-collector: - image: otel/opentelemetry-collector-contrib:0.115.0 + image: otel/opentelemetry-collector-contrib:0.150.1 container_name: apf-portal-otel-collector restart: unless-stopped command: ['--config=/etc/otel-collector.yaml'] -- 2.30.2