Dokploy healthcheck causes endless restart loop although the application is working.

To Reproduce

Description

My Dokploy instance enters an endless restart loop when the default healthcheck is enabled.

The strange part is that the application itself appears to be working correctly:

• Container logs look normal.
• No startup errors are visible.
• The web interface becomes accessible when the healthcheck is disabled.
• The issue seems to be limited to the healthcheck itself.

Current vs. Expected behavior

Steps to Reproduce

Current behavior:

1. Dokploy service starts.
2. Service remains in Starting.
3. Healthcheck eventually fails.
4. Docker marks the container as unhealthy.
5. Service restarts.
6. The cycle repeats indefinitely.

Workaround

Disabling the healthcheck immediately fixes the issue:

docker service update --no-healthcheck dokploy

docker service scale dokploy=0
sleep 10
docker service scale dokploy=1

After doing this:

• Dokploy starts successfully.
• The dashboard is accessible.
• All expected functionality appears to work normally.

Important Observation

The problem returns as soon as I restore the default healthcheck:

docker service update --health-cmd=default dokploy

docker service scale dokploy=0
sleep 10
docker service scale dokploy=1

The service immediately goes back to the restart loop.

Logs

I checked the container logs and did not find any obvious startup errors.

The logs appear essentially identical whether the healthcheck is enabled or disabled.

Because the application works correctly when the healthcheck is removed, I suspect the healthcheck may be producing false negatives or may not be compatible with my current environment.

Provide environment information

## Environment

* OS: Ubuntu 22.04
* Deployment: Docker Swarm
* Dokploy version: v0.29.7
* Docker version: v29.5.3
* VPS Provider: Contabo
* Arch: x86_64

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

Installation, Application, Databases, Docker Compose, Local Development

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

No source file or test is identified. Start by reproducing the default healthcheck failure in Docker Swarm on the reported environment, then inspect the configured healthcheck command and its results while the application remains accessible. Done means the service stays healthy and no longer enters the restart loop with the default healthcheck enabled.