ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #portainer
Learn how to deploy and manage multi‑container applications using Portainer Stacks, including Git integration, environment variable injection, and lifecycle management.
Learn how to use Portainer’s RBAC to give developers container‑deploy rights while keeping endpoint and template control in the hands of operators.
Learn how to use Portainer Stacks to deploy multi-container applications using Docker Compose, including Git synchronization and avoiding common volume path errors.
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 Determine whether Portainer should automatically roll back partially completed operations—such as incomplete image layers pulled during a registry pull—when a user invokes the Cancel button, or whether it should leave those artifacts intact and rely on manual cleanup. Constraints and Uncertainty Portainer’s current cancellation flow sends a DELETE signa
The goal is to confirm whether a password change for a local Portainer user, performed through the API endpoint /api/users/{id}/password, becomes effective for subsequent authentication requests without restarting the Portainer container, or whether the change only takes effect after a container restart. Current observations show that the UI appears to apply
When restoring a Portainer backup, the administrator imports an SQLite database file to recover stack definitions, user settings, and endpoint configurations. The current feature does not automatically verify that the imported file is intact or unaltered before it becomes the active database, leaving the verification step to the operator. This raises the que
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
docker