Version
latest
Unraid Version
7.2.4
Bug Description
This is maybe not a bug exactly but it is something that i think should work differently. For stacks that have multiple profiles the stack display will show "partial (x/y)" where x is the number of currently running containers and y is the number of containers in all profiles.
In the case of the stack below there are 2 profiles, the main profile has 1 container and is what runs all the time. The other two containers are in a second profile that normally are not running. The normal state of this stack is to have 1 of 3 containers running.
Expected Behavior
I would prefer to see the current state of stack in terms of all the created containers. Instead of reporting the number of running containers vs the number of containers defined in the stack file I would think it would be better to query all the created containers that are part of the stack (using labels) and report the number of them that are running vs the number that are stopped/paused. Since compose down (of a stack or profile) removes all its containers and compose up creates them the number of stopped or paused containers better relates to the health of the stack than any that are defined but not created.
Steps to Reproduce
Have a stack with containers in multiple profiles. Bring up one profile. View ui.
Relevant Logs
Compose
Additional Context
No response
Version
latest
Unraid Version
7.2.4
Bug Description
This is maybe not a bug exactly but it is something that i think should work differently. For stacks that have multiple profiles the stack display will show "partial (x/y)" where x is the number of currently running containers and y is the number of containers in all profiles.
In the case of the stack below there are 2 profiles, the main profile has 1 container and is what runs all the time. The other two containers are in a second profile that normally are not running. The normal state of this stack is to have 1 of 3 containers running.
Expected Behavior
I would prefer to see the current state of stack in terms of all the created containers. Instead of reporting the number of running containers vs the number of containers defined in the stack file I would think it would be better to query all the created containers that are part of the stack (using labels) and report the number of them that are running vs the number that are stopped/paused. Since compose down (of a stack or profile) removes all its containers and compose up creates them the number of stopped or paused containers better relates to the health of the stack than any that are defined but not created.
Steps to Reproduce
Have a stack with containers in multiple profiles. Bring up one profile. View ui.
Relevant Logs
Compose
Additional Context
No response