fix(infra): correct OTel collector image tag #59

Merged
julien merged 1 commits from fix/infra/otel-collector-image-tag into main 2026-05-08 20:41:01 +02:00
Owner

Summary

otel/opentelemetry-collector-contrib:0.115.0 doesn't exist — release 0.115 was published as 0.115.1 only. Same memory-not-Docker-Hub mistake as Jaeger in #58.

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

Pin to 0.150.1 (latest stable). The collector's stable-feature backward-compat covers our otel-collector.yaml (otlp receiver, batch processor, debug exporter, otlp/jaeger exporter) — no config change needed.

Postgres 17.2-alpine, Redis 7.4-alpine, pgweb 0.16.2 were verified against Docker Hub at the same time; they're all correct.

Test plan

  • cd infra/local && docker compose -f dev.compose.yml up -d — all 3 core services pull and start healthy.
  • --profile observability up -d adds Jaeger 1.76.0 (after #58).
  • --profile dbtools up -d adds pgweb 0.16.2.
  • docker compose ps shows everything healthy.
## Summary `otel/opentelemetry-collector-contrib:0.115.0` doesn't exist — release 0.115 was published as `0.115.1` only. Same memory-not-Docker-Hub mistake as Jaeger in #58. ``` Error response from daemon: failed to resolve reference "docker.io/otel/opentelemetry-collector-contrib:0.115.0": not found ``` Pin to `0.150.1` (latest stable). The collector's stable-feature backward-compat covers our `otel-collector.yaml` (otlp receiver, batch processor, debug exporter, otlp/jaeger exporter) — no config change needed. Postgres `17.2-alpine`, Redis `7.4-alpine`, pgweb `0.16.2` were verified against Docker Hub at the same time; they're all correct. ## Test plan - [ ] `cd infra/local && docker compose -f dev.compose.yml up -d` — all 3 core services pull and start healthy. - [ ] `--profile observability up -d` adds Jaeger 1.76.0 (after #58). - [ ] `--profile dbtools up -d` adds pgweb 0.16.2. - [ ] `docker compose ps` shows everything healthy.
julien added 1 commit 2026-05-08 20:37:34 +02:00
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
8f892972dc
`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.
julien merged commit d5c5c45175 into main 2026-05-08 20:41:01 +02:00
julien deleted branch fix/infra/otel-collector-image-tag 2026-05-08 20:41:01 +02:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: julien/apf_portal#59