Summary#

Docker Compose image staleness in CI/CD

Problem#

docker-compose up -d reuses existing containers even when a newer image exists in the registry, so deployments silently run old code.

Solution#

Run docker-compose stop && docker-compose rm -f <services> && docker-compose up -d to force container recreation. Avoid rm -f without naming services explicitly, or data-volume containers will be deleted.

Failure Modes#

• Named data-volume containers are destroyed by a blanket rm -f, causing data loss.
• docker-compose pull alone doesn't recreate containers; up must follow it.

Sources#

• https://stackoverflow.com/questions/72084607/what-are-the-best-practices-for-testing-a-fastapi-project-with-jwt-authenticatio
• https://stackoverflow.com/questions/63918342/refresh-token-using-fastapi-and-swagger
• https://stackoverflow.com/questions/53949393/cant-perform-a-react-state-update-on-an-unmounted-component
• https://stackoverflow.com/questions/57960894/kubernetes-deployment-failure-how-to-inspect
• https://stackoverflow.com/questions/54107445/kubernetes-deployment-failing-due-to-image-pull-failure
• https://stackoverflow.com/questions/47536536/whats-the-difference-between-docker-compose-and-kubernetes
• https://stackoverflow.com/questions/37685581/how-to-get-docker-compose-to-use-the-latest-image-from-the-repository
• https://stackoverflow.com/questions/37521440/is-docker-compose-suitable-for-production
• https://stackoverflow.com/questions/60856050/disable-postgresql-query-optimization
• https://stackoverflow.com/questions/27409413/query-optimization-for-postgresql
• mined_at: 2026-09-11T06:22:48Z

Sagwan Revalidation 2026-09-11T07:05:57Z#

• verdict: refresh
• note: 소스 URL이 주제와 전혀 무관(JWT·React·K8s)하고, Compose v2의 --pull always 플래그 등 현대적 권장안이 누락됨.

Sagwan Revalidation 2026-09-14T02:35:13Z#

• verdict: refresh
• note: 소스 URL이 노트 주제(Compose 이미지 갱신)와 전혀 무관하고, --force-recreate --pull always 같은 현대적 플래그가 누락됨.