Container with timezone mounts incorrectly shown as stopped

[monstermuffin]

🔍 Check for existing issues

• Completed

How is Dozzle deployed?

Standalone Deployment

📦 Dozzle version

v8.13.11

✅ Command used to run Dozzle

My Dozzle deployment is deployed via Ansible:

- name: Deploy Dozzle container for log monitoring
    community.docker.docker_container:
      name: labb0t-dozzle
      image: amir20/dozzle:latest
      pull: true
      recreate: true
      state: started
      networks:
        - name: labb0t_network
      volumes:
        - /var/run/docker.sock:/var/run/docker.sock:ro
      env:
        DOZZLE_AUTH_PROVIDER: forward-proxy
        DOZZLE_AUTH_HEADER_USER: X-Authentik-Username
        DOZZLE_AUTH_HEADER_EMAIL: X-Authentik-Email
        DOZZLE_AUTH_HEADER_NAME: X-Authentik-Name
        DOZZLE_LEVEL: debug
      restart_policy: unless-stopped
      labels:
        com.centurylinklabs.watchtower.enable: "true"

🐛 Describe the bug / provide steps to reproduce it

Container with timezone mounts (/etc/timezone:/etc/timezone:ro and
/etc/localtime:/etc/localtime:ro) is incorrectly classified as stopped in the Dozzle UI,
despite being running and actively producing logs.

Steps to reproduce:

1. Deploy Dozzle with standard configuration
2. Create a container with timezone mounts:

 volumes:
   - /etc/timezone:/etc/timezone:ro
   - /etc/localtime:/etc/localtime:ro

3. Container runs normally and produces logs (docker logs works fine)
4. In Dozzle UI, container appears as stopped and is not visible by default
5. Container only becomes visible when "Show stopped containers" option is enabled
6. Removing the timezone mounts fixes the issue, container appears as running and logs are shown

I destroyed the container and recreated it hoping a new Id would fix it, but the issue was the same.

💻 Environment

Client: Docker Engine - Community
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.4
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 11
  Running: 11
  Paused: 0
  Stopped: 0
 Images: 11
 Server Version: 27.5.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc version: v1.2.4-0-g6c52b3f
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.0-28-arm64
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 3.735GiB
 Name: app
 ID: db021ff6-4c7b-43e9-95ba-86625b1674d3
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: true
 Insecure Registries:
  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.

Container in question is dc0b4a2e84fc. Container was shown in the logs as can be seen below, but in the UI was shown as stopped with no logs able to be viewed:

  {"level":"debug","version":"v8.13.11","id":"dc0b4a2e84fc","time":"2025-09-01T15:21:20Z","m
  essage":"Finding container"}
  {"level":"debug","version":"v8.13.11","containers":11,"time":"2025-09-01T15:21:20Z","messa
  ge":"finished initializing container store"}

  {"level":"debug","version":"v8.13.11","event":"stop","id":"dc0b4a2e84fc","time":"2025-09-0
  1T15:23:12Z","message":"received container event"}
  {"level":"debug","version":"v8.13.11","event":"die","id":"dc0b4a2e84fc","time":"2025-09-01
  T15:23:12Z","message":"received container event"}
  {"level":"debug","version":"v8.13.11","id":"dc0b4a2e84fc","time":"2025-09-01T15:23:12Z","m
  essage":"container died"}
  {"level":"debug","version":"v8.13.11","event":"start","id":"dc0b4a2e84fc","time":"2025-09-
  01T15:23:12Z","message":"received container event"}
  {"level":"debug","version":"v8.13.11","id":"dc0b4a2e84fc","time":"2025-09-01T15:23:12Z","m
  essage":"Finding container"}
  {"level":"debug","version":"v8.13.11","event":"restart","id":"dc0b4a2e84fc","time":"2025-0
  9-01T15:23:12Z","message":"received container event"}

📸 If applicable, add screenshots to help explain your bug

No response

[amir20]

I can't imagine what could cause this. I think the only option is to reproduce it. So I'll create it locally to see if it happens.

The logs above suggest that the container has died.

What does docker ps show?

[amir20]

Hmm I wasn't able to reproduce this...

docker run -v /etc/timezone:/etc/timezone:ro -v /etc/localtime:/etc/localtime:ro amir20/echo -r

I think something else is going on in your setup.

Going to move this to discussion.