Stopped apps should still show in docker ps

Feature Requests
1

Problem/Justification
When I stop an app through the web UI, it appears to actually remove the underlying app from the system itself. If I run “docker ps”, the stopped app doesn’t show up. This works if I stop the app from the CLI with docker, but the app shows as “crashed” in the web UI. This makes it more difficult to automate applications with docker commands.

Impact
With the app still available through the docker CLI commands, it allows for more automation opportunities without having to go through truenas middleware to implement.

User Story
I could use scripts to start and stop apps based on certain criteria. It also allows for better insights of all apps currently on the system even if they aren’t showing through docker ps.

2

Another item on top of this, I have a plex container with a static IP in a docker network bridge so it works properly with the plex.direct url. When the container is stopped in truenas, it removes it completely from the docker stack causing the stack to assign the IP to other containers as needed. If the container was within the stack, but stopped, it would prevent the statically assigned IP from being assigned to other containers.