What's the longterm plan in regards to inspection of app containers?

[Glowtape]

It's nice to be able to run apps in container on my NAS. However one aspect I'm not really happy with is the sparse details about the state of the container, that being the lack of things in regards to runtime details, say interfaces and their IP addresses in the container, memory usage, CPU usage (maybe incl. history) and so on. The details pane in the app section is currently rather light in actual details. It seems that this kind of info is readily available to kubectl.

Are there already plans to improve this situation?

(One of the reason I'd still prefer a solution like Portainer on plain Docker. The only reason I stopped doing the homebrew approach, starting with Cobia, is that it's getting more and more a pain in the butt to (re-)set up every update.)

 

[Patrick M. Hausen]

You can install TrueCharts' portainer app ...

 

[Glowtape]

That'll interact properly with k3s in the base system, or does that just nest a Docker environment within an app container? If it's latter, I'd prefer not run a Rube Goldstein type of system.

I used to disable k3s pre-Cobia and ran Docker straight.

 

[truecharts]

That'll interact properly with k3s in the base system, or does that just nest a Docker environment within an app container? If it's latter, I'd prefer not run a Rube Goldstein type of system.

I used to disable k3s pre-Cobia and ran Docker straight.

That can only manage k3s by design.