Resource usage not showing #4188

arifroni · 2025-10-14T13:14:07Z

arifroni
Oct 14, 2025

🔍 Check for existing issues

Completed

How is Dozzle deployed?

Standalone Deployment

📦 Dozzle version

v8.14.4

✅ Command used to run Dozzle

docker compose up -d

🐛 Describe the bug / provide steps to reproduce it

I have deployed dozzle in a proxmox LXC (alpine linux), and several other dozzle agents in several other proxmox LXC (alpine linux and ubuntu). But none of them are showing any mem or CPU usage.

docker compose file

  dozzle:
    restart: always
    image: amir20/dozzle:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 8080:8080
    environment:
      - DOZZLE_REMOTE_AGENT=192.168.1.152:7007,192.168.1.153:7007,192.168.1.155:7007,192.168.1.161:7007,192.168.1.163:7007,192.168.1.164:7007
      - DOZZLE_ENABLE_ACTIONS=true

💻 Environment

Client:
 Version:    28.3.3
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.24.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.40.0
    Path:     /root/.docker/cli-plugins/docker-compose

Server:
 Containers: 14
  Running: 12
  Paused: 0
  Stopped: 2
 Images: 13
 Server Version: 28.3.3
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: c787fb98911740dd3ff2d0e45ce88cdf01410486
 runc version: 4ca628d1d4c974f92d24daccb901aa078aad748e
 init version: 
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.14.11-1-pve
 Operating System: Alpine Linux v3.22
 OSType: linux
 Architecture: x86_64
 CPUs: 1
 Total Memory: 2GiB
 Name: docker-monitor
 ID: 92d9f089-6393-4fd8-8d61-7ab7e24987b0
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

📜 Dozzle logs are required for debugging purposes. You may need to enable debug mode. See https://dozzle.dev/guide/debugging.

2025-10-14T13:02:36Z DBG starting to stream stats | version=v8.14.4 container=f63ce84edd47 host=docker-monitor
2025-10-14T13:02:36Z DBG Fetching host | version=v8.14.4 host=docker-monitor
2025-10-14T13:02:36Z DBG starting to listen to docker events | version=v8.14.4 host=docker-monitor
2025-10-14T13:02:36Z DBG Fetching host | version=v8.14.4 host=docker-monitor
2025-10-14T13:02:36Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:36Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:37Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:38Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:38Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:38Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:38Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c redis-cli ping || exit 1 id=d5c7fed13b25
2025-10-14T13:02:38Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c redis-cli ping || exit 1 id=d5c7fed13b25
2025-10-14T13:02:39Z DBG container event from store | version=v8.14.4 event=exec_die id=d5c7fed13b25
2025-10-14T13:02:39Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:39Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:39Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:40Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:40Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:40Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:41Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:41Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:41Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:42Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:42Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:42Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:43Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:43Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:43Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:44Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:44Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:44Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:45Z DBG received container event | version=v8.14.4 event=exec_create: /bin/sh -c wget --no-verbose --tries=1 --spider http://localhost:8080 || exit 1 id=4020e9288953
2025-10-14T13:02:45Z DBG received container event | version=v8.14.4 event=exec_start: /bin/sh -c wget --no-verbose --tries=1 --spider http://localhost:8080 || exit 1 id=4020e9288953
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c wget --no-verbose --tries=1 --spider http://localhost:8080 || exit 1 id=4020e9288953
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c wget --no-verbose --tries=1 --spider http://localhost:8080 || exit 1 id=4020e9288953
2025-10-14T13:02:45Z DBG received container event | version=v8.14.4 event=exec_die id=4020e9288953
2025-10-14T13:02:45Z DBG container event from store | version=v8.14.4 event=exec_die id=4020e9288953
2025-10-14T13:02:46Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:46Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:46Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c curl --silent --fail http://localhost:9880/ || exit 1 id=76db606697e7
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c curl --silent --fail http://localhost:9880/ || exit 1 id=76db606697e7
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_die id=76db606697e7
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:47Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:48Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:48Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:48Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:49Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:49Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:49Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:50Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:50Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:51Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:51Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c immich-healthcheck id=b1e9f8fdb02b
2025-10-14T13:02:51Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c immich-healthcheck id=b1e9f8fdb02b
2025-10-14T13:02:51Z DBG container event from store | version=v8.14.4 event=exec_die id=b1e9f8fdb02b
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c /usr/local/bin/healthcheck.sh id=ae51cc086bf2
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c /usr/local/bin/healthcheck.sh id=ae51cc086bf2
2025-10-14T13:02:52Z DBG container event from store | version=v8.14.4 event=exec_die id=ae51cc086bf2
2025-10-14T13:02:53Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:53Z DBG container event from store | version=v8.14.4 event=exec_start: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
2025-10-14T13:02:53Z DBG container event from store | version=v8.14.4 event=exec_die id=9876cfe07600
2025-10-14T13:02:54Z DBG container event from store | version=v8.14.4 event=exec_create: /bin/sh -c pg_isready -d litellm -U llmproxy id=9876cfe07600
```

### 📸 If applicable, add screenshots to help explain your bug

_No response_

amir20 · 2025-10-14T15:29:05Z

amir20
Oct 14, 2025
Maintainer

I don't what could be causing this. There were some similar issues but I don't think they are related. Here is a few ideas:

I have personally never tested this on Alpine. I would first run a Dozzle instance without agent to isolate the problem. It might be related to Alpine.
I do tested regularly on Ubuntu. So I wonder if there is something wrong on the UI not streaming it correclty.
Does docker stats work?
How are the agents deployed? Are they behind a proxy?
Finally, there is an FAQ that might relevant.

Good luck. Let me know if you find anything. I won't be able to help much without anything obvious to investigate.

6880

0 replies

arifroni · 2025-10-14T20:01:10Z

arifroni
Oct 14, 2025
Author

I don't what could be causing this. There were some similar issues but I don't think they are related. Here is a few ideas:

I have personally never tested this on Alpine. I would first run a Dozzle instance without agent to isolate the problem. It might be related to Alpine.

I do tested regularly on Ubuntu. So I wonder if there is something wrong on the UI not streaming it correclty.

Does docker stats work?

How are the agents deployed? Are they behind a proxy?

Finally, there is an FAQ that might relevant.

Good luck. Let me know if you find anything. I won't be able to help much without anything obvious to investigate.

thanks for the suggestions.

I tested without any agents, problem doesnt go away.
docker stats shows 0 cpu and 0 mem.
i created ubuntu lxc and there docker stats works. and dozzole also works. so i guess it might have to do with alpine+docker combo.

0 replies

amir20 · 2025-10-14T20:20:33Z

amir20
Oct 14, 2025
Maintainer

docker stats shows 0 cpu and 0 mem

Then there you go. If stats is not working then Dozzle won't work either.

0 replies

amir20 · 2025-10-14T20:21:21Z

amir20
Oct 14, 2025
Maintainer

Moving this to discussion.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Resource usage not showing #4188

Uh oh!

{{title}}

Uh oh!

Replies: 4 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Resource usage not showing #4188

Uh oh!

arifroni Oct 14, 2025

🔍 Check for existing issues

How is Dozzle deployed?

📦 Dozzle version

✅ Command used to run Dozzle

🐛 Describe the bug / provide steps to reproduce it

💻 Environment

📜 Dozzle logs are required for debugging purposes. You may need to enable debug mode. See https://dozzle.dev/guide/debugging.

Replies: 4 comments

Uh oh!

Uh oh!

amir20 Oct 14, 2025 Maintainer

Uh oh!

arifroni Oct 14, 2025 Author

Uh oh!

amir20 Oct 14, 2025 Maintainer

Uh oh!

amir20 Oct 14, 2025 Maintainer

arifroni
Oct 14, 2025

amir20
Oct 14, 2025
Maintainer

arifroni
Oct 14, 2025
Author

amir20
Oct 14, 2025
Maintainer

amir20
Oct 14, 2025
Maintainer