Portainer

• Container stoppedRuns when a container stops, crashes or is restarting after a crash, or only when it fails, with its exit code. Containers already stopped when the workflow is turned on don't run it.
• Container unhealthyRuns when a container's health check starts failing, with what the check printed. Containers already unhealthy when the workflow is turned on don't run it.
• Container back upRuns when a container that was stopped or unhealthy is running again, and healthy if it has a health check, such as to close an alert.

• List environmentsList the Docker and Kubernetes environments Portainer manages, with whether each is up and how many containers are running, stopped and unhealthy.
• List containersList the containers in an environment, running and stopped, by state, name or stack, with their status, health and image.
• Get containerLook up a container's status: whether it's running, its health and last health check, exit code, when it started and stopped, restarts, image and ports.
• Get container logsRead a container's recent logs: its last lines, or those since a time, output and errors or one of them, such as to post to a channel when it fails.
• Start containerStart a stopped container. One already running is left as it is.
• Stop containerStop a running container, letting it shut down first. One already stopped is left as it is.
• Restart containerRestart a container, such as when it stops answering, from an alert or a chat command. A stopped one is started.
• Recreate containerReplace a container with a new one from the same settings, pulling the newest image of its tag first, to update it. It gets a new ID.
• Remove unused imagesFree disk space by removing images no container uses: untagged ones, or every unused one, optionally only those older than some hours.
• List stacksList the stacks Portainer deploys, in every environment or one, with whether each is running, its Git repository and commit, and when it last changed.
• Redeploy stackRedeploy a stack: one from Git with its newest commit, one made in Portainer as it is, optionally pulling newer images and setting environment variables.
• Update stackChange a stack's compose file, or set or remove its environment variables, and redeploy it. A stack from Git takes only variables; its file comes from the repository.
• Start stackStart a stopped stack's containers. One already running is left as it is.
• Stop stackStop a stack's containers, keeping the stack to start again later. One already stopped is left as it is.

No actions match that.