ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #portainer
We manage several Docker hosts through Portainer CE and want alerting on container and endpoint health. Since CE has no built-in notification engine, we plan to use external tooling (Prometheus/Alertmanager or a lightweight health-check script polling the Portainer API) against the same endpoints Portainer already inventories. The unresolved decision is seve
Portainer Stacks maintain repeatable Docker Compose development environments from Compose files stored in Git repositories or entered in the UI. An unresolved question concerns what happens when a stack redeploy fails partway, such as when an updated image reference is invalid, and whether the previous environment is restored automatically. Documented behavi
When utilizing the Portainer Edge Agent to manage remote environments, the central instance relies on periodic polling to reflect the current status of hosted containers. However, there is uncertainty regarding the consistency of state updates when actions occur outside of the Portainer UI. If a container is stopped, started, or restarted directly via the Do
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
A Portainer CE 2.x deployment serves its web UI on port 9000, and when that port is published on all interfaces the instance can become reachable from networks that should never see it. The decision is where access control should live: inside Portainer or in a layer in front of it. Portainer provides built-in username/password authentication and, in recent r
The goal is to safely retry failed API calls through Portainer without causing duplicate writes when interacting with the Docker daemon via the /api/endpoints/{id}/docker proxy. Portainer documents that create/update operations are idempotent when the request includes a stable identifier, and that conditional requests using If‑Match/ETag prevent duplicate wr
I'm consolidating a low-traffic internal stack onto cheaper nodes in a Docker Swarm managed through Portainer. The plan is to label two small nodes (for example tier=low ) and use placement constraints plus CPU/memory limits in the stack definition so these services never land on the larger nodes and never consume more than a fixed share of resources. What I
Goal: Ensure that disabling Portainer’s built‑in scheduler does not leave residual labels that could trigger unintended container restarts. When the scheduler is active, Portainer adds labels such as io.portainer.scheduler.action to managed containers to track the desired scaling state. Disabling the scheduler through the UI or API does not automatically rem
I want to exercise Portainer's integration flows (endpoint listing, registry connections, stack deployment) in an isolated test instance without ever touching production secrets. My plan is a fresh portainer-ce container with its own data volume, a throwaway registry configured with dummy credentials via the built-in "Test connection" button, and a limited-s
docker
prometheus
kubernetes