[MOVED TO ROADMAP] Display non-ix managed stacks and containers on apps screen

[Stux]

Electric Eel includes Docker, and Docker Compose is used to power the apps

The apps screen displays IX managed stacks.

It would be helpful to also view non-IX managed stacks, and non stack containers.

They could be displayed with generic icons, and the Details information could show generic information.

docker has a property on all stacks which defines their stack, and containers without this property are not stacks.

This would allow a user to understand what containers and stacks are running on their hosted docker instance, which are not IX apps.

In my example, I have the Dockge app installed… and it has created two stacks, one for Jellyfin, and the other for nginx.

BUT there is no visibility that these are running from the Applications pane, although I think there could be.

Note, dockge has similar functionality, ie it shows stacks that are not managed by dockge… and if you click on it, it says “not managed by dockge”

Perhaps the display of these stacks could be hidden behind a radio button, much like how extra snapshot columns are hidden behind a radio button

[Captain_Morgan]

Is it better to manage the unmanaged

or

make it easier for everything to be managed?

I know our QA team would prefer the latter.

[mull.codes]

I have created a jira for the same, please check, it was created as a bug but seems like it is a feature request. Dev team please convert the issue to a feature. Thanks.

https://ixsystems.atlassian.net/browse/NAS-131621

[mull.codes]

My understanding was that, because there is only one instance of docker on the host machine and portainer is just a tool to compose. Any container created here would reflect back in the Apps page. Unfortunately I don’t see that.

I can see all the images portainer downloaded to create container from the UI:

Now going to the Shell I can see both images and containers

I should be able to see the same in the Apps page but apps doesn’t doesn’t reflect this.

I did some test to see if Portainer picks up everything from below command

And it did. Portainer can’t edit this container and I don’t expect it to either. The same goes for TrueNAS EE.

Any compose manager tool will read docker ps regardless of where it came from. TrueNAS Electric Eel should be able to manage features like:

1. Start
2. Stop
3. Remove

Below is ss of Portainer managing container created in TrueNAS Electric Eel

I don’t expect TrueNAS Electric Eel be able to edit this. But having it listed is must. After all it’s the same instance of docker.

[GuyFromMars]

So we’re at 70 votes. @Captain_Morgan is this still a possibility? Portainer, Arcane, Dockge, etc can all display running docker containers already running, why does TrueNAS not do the same? If you’re QA wants less support headache, just have a warning icon on the apps dashboard that a given app wasn’t started by TrueNAS & therefore cannot me mamaged. I think that’s a reasonable request.

[Captain_Morgan]

@GuyFromMars

is this still a possibility?

Yes, its on the list of projects we’d like to get done. For a good user experience, it does require some plumbing to store the images that is different from Apps.

(Edit: this comment was really referring to the custom icons for custom docker apps).

[shoulders]

Can you. Change the thread title to accept or what is suitable. People can then get their votes back.

[ABain]

Update: Moved to Roadmap for Assessment

Great news! This feature request has gathered enough community interest to be transferred to our internal roadmap for detailed scoping and assessment.

What this means:

• Our product team will now evaluate technical feasibility, resource requirements, and alignment with our product strategy
• This request is now closed for voting, and your votes have been released back to use on other requests
• We’ll conduct a thorough analysis to determine if and how this feature might be implemented
• Please note that transfer to the roadmap doesn’t guarantee implementation - some features may not proceed based on our assessment findings; however, we will update this thread once a decision has been made.

Thank you to everyone who voted and contributed to the discussion. Your input has been invaluable in helping us understand the community’s needs and use cases for this feature.

[ABain]

WIP screen mock-up.