Container Stats Fails #3
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please do not mark this stale my friend bot |
I have the same problem. New user of portainer, clicked on stats tab and got error as above. No stats shown. Plain install of HassOS on RPI 3b+ 0.82 |
same problem here. |
i have the same problem |
the issue here. I get this also within command line executing a "docker top" command:
|
Mine tells me
Edit: Maybe somewhat related to portainer/portainer#616. The reporter there was apparently able to set the arguments with a Docker image. Perhaps something similar would work here? |
Should this work in 0.5.0? I just tried and still get the same error. |
it should, as per screenshots above. Could you please provide me with your system details? (shown in the startup of the add-on, in the logs). |
re-opening issue to see what @tboyce021 comes up with. |
Mine is actually probably a HassOS issue. I just thought to try it on the host itself and get the same
Edit: This is using the VMDK with Proxmox on a NUC. |
still don't work with 0.5.0 (same error as before) |
Here what I get logging into portainer itself via console:
|
Makes sense, the daemon does this on the host level, so this indicates the |
Sounds like this isn't going to be fixed on HassOS. Is there a way to make Portainer use the HassOS API or is this just going to remain broken for HassOS? |
I'm not sure the HassOS API is sufficient for this anyway. I only see a way to get stats for the supervisor, HA, and add-ons, but I don't see a way to get stats for any container installed outside of that (i.e. using Portainer itself). |
Any idea who we could ask in the dev team about adding the ps command to HassOS? This is a valuable tool for tracking down excessive resource use. |
HassOS uses buildroot to configure the system. It should be a relatively simple matter of tracking down which buildroot package contains the full I may have some time this weekend to do a sample build of HassOS and see if that addresses this issue. Disclaimer, I'm not a core dev and have little to no influence. But, if it works I will create a pull-request and see if it is accepted. |
FYI, it does have |
I built the work-in-progress HassOS dev branch (3.1) with PROCPS_NG enabled and that does seem to fix portainer stats: I will create a PR in HassOS and see if it goes anywhere. |
portainer requires ability to run 'ps -e' which is not supported by busybox's ps. This fixes hassio-addons/addon-portainer#3 Tested on odroid_xu4 target.
portainer requires ability to run 'ps -e' which is not supported by busybox's ps. This fixes hassio-addons/addon-portainer#3 Tested on odroid_xu4 target.
The pull request with the fix was accepted into the dev branch for HassOS 3.1 -- I do not know how long it will be before the 3.x branch goes live for general users, but it will eventually be in the base. |
portainer requires ability to run 'ps -e' which is not supported by busybox's ps. This fixes hassio-addons/addon-portainer#3 Tested on odroid_xu4 target.
Just updated HASSOS to Release 2.12. And now it is really working. Well done! |
Confirmed. Nicely done. |
Nice! Closing issue! 👍 |
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread. |
Problem/Motivation
STATS function is broken
Expected behavior
Showing Container CPU/Memory Stats
Actual behavior
Get Error Message: Error running ps: exit status 1
Steps to reproduce
Point to container, and click stats icon.
The text was updated successfully, but these errors were encountered: