Bug: Local server health check can't detect custom default-address-pools #5383

To Reproduce

1. Self-host Dokploy via install.sh
2. On the host, configure a custom pool, e.g. in /etc/docker/daemon.json:

{"default-address-pools": [{"base": "10.10.0.0/16", "size": 28}]}

3. In the Dokploy dashboard, go to the local/main server's Server → Docker → Health tab.

Current vs. Expected behavior

Expected: since a custom default-address-pools is genuinely configured and active, the health tab should show "Custom pool detected on this server."

Observed: it always shows the generic default text, never the custom-pool notice.

Cause: getServerHealth (packages/server/src/services/server-health.ts) reads the config for the local server (no serverId) via execAsync, running inside the Dokploy container itself, not on the host. The health script does cat /etc/docker/daemon.json, but install.sh's docker service create --name dokploy only mounts docker.sock, /etc/dokploy, and a /root/.docker volume, not /etc/docker. So the read always fails silently and addressPools stays null.

Provide environment information

OS: Rocky Linux
Arch: x86_64
Dokploy version: 0.30.5

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

Docker

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

Same server where Dokploy is installed

Additional context

networkCount in the same health check is correct (it goes through docker network ls -q via the already-mounted docker.sock), only the daemon.json read is broken.

Suggested fix: use docker info --format '{{json .DefaultAddressPools}}' instead of cat /etc/docker/daemon.json, goes over the same already-mounted socket, no new mount needed:

$ docker info --format '{{json .DefaultAddressPools}}'
[{"Base":"10.10.0.0/16","Size":28}]

Just adjust the field names in the parsing code (Base/Size instead of base/size).

Will you send a PR to fix it?

No