Docker Swarm rolling update on Raspberry Pi leaves in‑memory cache stale after task replacement
Goal: achieve a zero‑downtime migration of a small application on a Raspberry Pi Docker Swarm cluster while preserving any in‑memory state such as caches or session data during a rolling update. Constraint: Docker Swarm’s rolling update mechanism drains the old task, waits for the replacement to become healthy, and then proceeds, but it provides no built‑in
raspberrypi