ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
The goal is to confirm whether secrets defined in a Docker Compose file are actually created when a stack is deployed through Portainer using a Compose version string of 3.9 or newer. The Portainer interface does not emit a warning about version incompatibility; any diagnostics appear only in the server or agent logs, which creates uncertainty about whether
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
kubernetes