From 6945f76319fd1440f17512725c56bfd4dfd71d99 Mon Sep 17 00:00:00 2001 From: Chiro Hiro Date: Thu, 4 Jun 2026 17:08:59 +0800 Subject: [PATCH] Bump docker-compose images to latest stable and pin them MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit redis used the floating :latest tag while postgres (:16) and rabbitmq (:4.0.6-management) were pinned to older releases. Floating or stale tags make local infra non-reproducible — a new upstream release can change behaviour (including the healthchecks) on an unrelated day. Update every service to its current latest-stable release and pin it, keeping each image's existing pin granularity: - postgres 16 -> 18 (18.4 latest; major pin, as before) - redis latest -> 8 (8.8.0 latest stable; 8.8-rc1 is a release candidate) - rabbitmq 4.0.6-management -> 4.3.1-management (latest stable patch, keeps the management variant) Note: bumping postgres from 16 to 18 is a major upgrade — an existing postgres_data volume initialised by 16 must be recreated (or migrated with pg_upgrade) before 18 will start. This is fine for ephemeral local dev infra. Closes #46 --- docker-compose.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docker-compose.yaml b/docker-compose.yaml index c13532b..00be0a8 100644 --- a/docker-compose.yaml +++ b/docker-compose.yaml @@ -2,7 +2,7 @@ version: "3.9" services: postgres: - image: postgres:16 + image: postgres:18 restart: unless-stopped container_name: postgres environment: @@ -24,7 +24,7 @@ services: start_period: 10s redis: - image: redis:latest + image: redis:8 container_name: redis restart: unless-stopped ports: @@ -42,7 +42,7 @@ services: start_period: 5s rabbitmq: - image: rabbitmq:4.0.6-management + image: rabbitmq:4.3.1-management restart: unless-stopped container_name: rabbitmq environment: