Dokploy shows running container as not running (no green icon and cannot stop)

To Reproduce

Use this compose:

services:
  agent-zero:
    image: agent0ai/agent-zero
    container_name: agent-zero
    ports:
      - "21671:80"
    volumes:
      - agent_zero_data:/a0/usr
      - /opt/flutter:/opt/flutter:ro
    extra_hosts:
      - "host.docker.internal:host-gateway"
    restart: unless-stopped

volumes:
  agent_zero_data:
    driver: local

Deploy it.
Stop it.
Restart docker.
Go to log tab to observe the container is running but the compose app doesn't have green icon and the stop button cannot be tapped.

Current vs. Expected behavior

Expected: The app has green icon and the stop button can be tapped.

Provide environment information

OS: Arch Linux x86_64
Kernel: Linux 7.0.11-1-cachyos-bore
Dokploy: v0.29.8

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

Start from the Docker Compose log tab and reproduce the reported lifecycle: deploy the supplied compose file, stop it, restart Docker, and inspect the container status. Trace how the running container state controls the green icon and stop button; done means the app reflects the running state and allows the container to be stopped.