Replies: 14 comments 3 replies
-
I see you are on rpi. Seems to be related to https://dozzle.dev/guide/faq#i-installed-dozzle-but-memory-consumption-doesn-t-show-up |
Beta Was this translation helpful? Give feedback.
-
well funily enough, memory consumption shows up albeit it takes some time to be processed : |
Beta Was this translation helpful? Give feedback.
-
ah then I don't know 🫤 I don't have RPI handy to test it. Does |
Beta Was this translation helpful? Give feedback.
-
I use podman and podman stats works fine |
Beta Was this translation helpful? Give feedback.
-
I use Docker API directly. So if you could use the Docker CLI and test with it then that's the best way to know what is happening. I have deployed Podman here and there but it has always been a pain on Mac so I just use Orbstack now. Let me know what you find. |
Beta Was this translation helpful? Give feedback.
-
I will try with docker and a few containers to see if the issue is related to podman or raspbian |
Beta Was this translation helpful? Give feedback.
-
Okay, I tried Dozzle with docker and cpu and ram stats are correctly displayed Docker query :
Podman query :
Regarding the version of each :
I hope all the details provided here make sense and will help you isolate the problem Also, please apologize if anything I say is not clear, English is not my first language :) |
Beta Was this translation helpful? Give feedback.
-
Hey @t4nki so it seems like Podman is the culprit. Docker API returns the right data, while podman returns all zeros for CPU. I don't think there is anything I can do on my side to fix it. There wasn't a lot either reported on this. I found this issue portainer/portainer#4818. I assume not a lot of people use RPI and Podman. I think this is an unfortunate parts of using Podman some times. |
Beta Was this translation helpful? Give feedback.
-
I guess dozzle tries to retrieve precpu{} values, am I right ? |
Beta Was this translation helpful? Give feedback.
-
Yes, see dozzle/internal/docker/client.go Lines 231 to 232 in 4cfd3d0 |
Beta Was this translation helpful? Give feedback.
-
I see, let's hope this will be fixed in future versions, podman on Debian is pretty outdated anyway Did you have time to have a look at the grouping bug I talked about in the first post ? |
Beta Was this translation helpful? Give feedback.
-
Going to move this to discussion since it's not a Dozzle bug.
It should work as documented https://dozzle.dev/guide/container-groups#custom-groups I am not sure what you mean by not working. I may have a bug because I changed custom groups recently but was working. It works there with |
Beta Was this translation helpful? Give feedback.
-
I can confirm that in the Podman environment containers are not grouped in the user interface. I'm sure my configuration based on the 'dev.dozzle.group' label worked before, but it stopped working a few days ago. I tried downgrading Dozzle to bi-sect the problem but I failed. |
Beta Was this translation helpful? Give feedback.
-
it has never worked for me, but, I'm a fresh dozzle user (for the last month I might say) |
Beta Was this translation helpful? Give feedback.
-
🔍 Check for existing issues
How is Dozzle deployed?
Standalone Deployment
📦 Dozzle version
8.10.4
✅ Command used to run Dozzle
Dozzle is deployed through Ansible:
🐛 Describe the bug / provide steps to reproduce it
The CPU average is always 0 be it global or containers
Also, I group my containers in pods (my main raison for using podman BTW) I tried using dev.dozzle.group label but i does not seem to be honored by dozzle
but, by accessing /group/<my_group> it works fine :)
Could you take a look at this, it's not a critical issue, it's just that it could be useful
Other than that, dozzle works like a charm and it's a great piece of software 👍
💻 Environment
📸 If applicable, add screenshots to help explain your bug
No response
📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.
No response
Beta Was this translation helpful? Give feedback.
All reactions