From 4189add2f7349a9c7b42faa8c6143719c9371bd1 Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Sat, 15 May 2021 12:19:48 +0000 Subject: [PATCH] Temporarily pin haproxy image to 2.3 The haproxy 2.4 images aren't working for us, docker-compose perpetually reports the container in a "restarting" state. Pin back from latest to 2.3 until we can sort out what needs to change in how we integrate this on the server. Change-Id: I01ae11a31eb8eaeb9e570692d5ec268395f69a97 --- playbooks/roles/haproxy/files/docker/docker-compose.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/haproxy/files/docker/docker-compose.yaml b/playbooks/roles/haproxy/files/docker/docker-compose.yaml index b4e0bac2b2..dab8446f1c 100644 --- a/playbooks/roles/haproxy/files/docker/docker-compose.yaml +++ b/playbooks/roles/haproxy/files/docker/docker-compose.yaml @@ -5,7 +5,7 @@ version: '2' services: haproxy: restart: always - image: docker.io/library/haproxy:latest + image: docker.io/library/haproxy:2.3 network_mode: host volumes: - /dev/log:/dev/log