Registry Credentials Not Applied to Remote VPS

To Reproduce

1. Configure running on a server of your choosing
2. Configure Dokploy with remote VPS target
3. Add private registry credentials in Dokploy UI
4. Create docker-compose project referencing private image
5. Deploy to remote VPS
6. Observe authentication failure

Current vs. Expected behavior

Current Behavior

1. Registry credentials added in Dokploy UI:

   • Registry: ghcr.io
   • Username: my_gh_username
   • Credentials: GitHub Token following the docs

2. Docker Compose deployment with private image fails:
   mdm-api Error Head "https://ghcr.io/v2/my_gh_username/myrepo/my_image/manifests/latest": unauthorized

3. Checking ~/.docker/config.json on VPS shows no ghcr.io entry or more rightly said no file at all

Expected Behavior

Registry credentials should either:

• Be automatically synced to remote VPS Docker config, OR
• Be injected via docker-compose auth mechanisms, OR
• Documentation should clarify manual login is required for remote deployments

Provide environment information

### Environment
  - **Dokploy Setup:** Control panel on one local machine running on ubuntu:24, deployments on remote VPS running ubuntu 24
  - **Deployment Type:** Docker Compose
  - **Registry:** GitHub Container Registry (ghcr.io)
  - **Dokploy Version:** v0.25.3

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?

Remote server

Additional context

Workaround

Manual SSH to VPS and login:

docker login ghcr.io -u ...

Will you send a PR to fix it?

No

No specific file or test is named in the report. Start at the Docker Compose deployment path for remote VPS targets and trace how UI registry credentials are passed to the remote Docker daemon. Done means a private ghcr.io image deploys without manual login, or the required manual login is clearly documented.