From 84bda251dd63eb7591735e5d2c1218bfaa2f204a Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Wed, 3 Jul 2024 11:33:46 -0700 Subject: [PATCH] Use jaeger all-in-one v1 image It looks like the :latest image may be the head of the main branch, which is cool, we do that too, but apparently Jaeger does not test their releases with Zuul, and it appears they have merged something that breaks our usage for it. They may be starting v2 development and thus may be intentionally merging backwards incompatible changes. To address this, use the :1 image tag, so that we are still compatible with Zuul. Change-Id: I7f9602fbd2d98502c5c88641f61b4e408aa1525d --- playbooks/roles/jaeger/templates/docker-compose.yaml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/jaeger/templates/docker-compose.yaml.j2 b/playbooks/roles/jaeger/templates/docker-compose.yaml.j2 index d9388ba584..8a8b7303cb 100644 --- a/playbooks/roles/jaeger/templates/docker-compose.yaml.j2 +++ b/playbooks/roles/jaeger/templates/docker-compose.yaml.j2 @@ -4,7 +4,7 @@ version: '2' services: jaeger: - image: docker.io/jaegertracing/all-in-one:latest + image: docker.io/jaegertracing/all-in-one:1 network_mode: host restart: always environment: