Stopping containers from within Portainer flags those containers as unhealthy
Author: cronald-sysCreated Sep 8, 2026Updated Sep 14, 2026
Labelskind/bugbug/need-confirmationbot/triage-complete
Before you start please confirm the following.
- Yes, I've searched similar issues on GitHub.
- Yes, I've checked whether this issue is covered in the Portainer documentation.
Problem Description
Stopping any healthchecked container from Portainer causes the environment dashboard to count it as unhealthy until the same container is started .
Containers stopped through other means (EG, TrueNAS Scale Apps management) do not report as unhealthy.
Expected Behavior
The stopped container should not be counted as unhealthy
Actual Behavior
The stopped container is marked unhealthy, but docker does not agree
Steps to Reproduce
Stop a container from the WebUI, then run curl -sS -G -H "X-API-Key: $PKEY" --data-urlencode 'all=1' --data-urlencode 'filters={"health":["unhealthy"]}'
Portainer logs or screenshots
See steps to reproduce
Portainer version
2.45.0
Portainer Edition
Community Edition (CE)
Platform and Version
Docker 28.3.1
OS and Architecture
TrueNAS Scale 25.10.6, AMD64
Browser
Brave 1.94.121
What command did you use to deploy Portainer?
It is deployed as a TrueNAS Scale app.Additional Information
No response
Source: portainer/portainer