ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Traefik Mesh enables canary releases on Docker Swarm by splitting HTTP traffic between service versions using weight labels. This guide shows the exact label configuration, verification steps, protocol limits, and common mistakes to avoid.
Shift traffic between stable and canary Docker Swarm services using Traefik Mesh weighted labels—without a hard cutover.
Portainer's Swarm stack deployment turns opaque SSH-and-CLI deploys into a shared, auditable workflow. Here's how it works, a concrete example, and where it falls short.
Learn how to run Mattermost in high‑availability mode using Docker Swarm, with shared PostgreSQL and MinIO, automatic failover, and the trade‑offs you must manage.
A decision guide for choosing Portainer’s UI to deploy Docker Compose stacks in Swarm mode, with a comparison table, trade‑offs, step‑by‑step implementation, and verification steps.
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
Migrating a small application in Docker Swarm without downtime relies on the documented rolling update capability of docker service update . The default stop-first order terminates the old task before starting its replacement, which causes a brief outage. Switching to --update-order start-first is intended to avoid that gap by starting the new task before th
Recently, we had an outage due to Redis being unable to write to a file system (not sure why it's Amazon EFS) anyway I noted that there was no actual HEALTHCHECK set up for the Docker service to make sure it is running correctly, Redis is up so I can't simply use nc -z to check if the port is open. Is there a command I can execute in the redis:6-alpine (or n
Goal: Clarify whether Portainer applies concurrent updates to the same logical stack on a Docker Swarm endpoint and a Kubernetes endpoint as independent operations or attempts to synchronize versioning between the two platforms. Constraints: The Portainer documentation up to version 2.19 does not specify how simultaneous stack updates are handled across orch
answered · 23 Jul 2022, 00:59 UTC
traefikmesh
raspberrypi
docker
redis
kubernetes