Create application service with Dockerfile provider from private ghcr.io account

[johngrimsey]

To Reproduce

• Add ghcr.io registry login to cluster settings, selecting external server
• Create new Application service on external server
• Choose Docker provider
• Use private registry credentials (Docker image, username, password)
• Click deploy

Current vs. Expected behavior

Current behaviour

Deploy fails to pull image from registry

## Expected behaviour

Specifying login details on the Provider panel should allow image to be pulled for deployment, whether on external server or Dokploy server.

Provide environment information

Dokploy 0.9.4

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

Docker

Additional context

Unsure if there is a relationship between the registry details in the Cluster Settings, and the login details on the provider panel.

[Siumauricio]

In the latest version we add a option to login in the remote server, have you tried?

[johngrimsey]

Yep did that first! Now works great with docker-compose in 0.9.4. Not working deploying a single Dockerfile from a remote registry, putting the credentials into the provider box (even after setting creds in registry settings under settings > cluster). Works on Dokploy server but not to external server.

[Siumauricio]

Strange, I tested with dockerhub in remote server and is working fine, can you follow this steps to configure the ghrc registry?

#478 (comment)

[johngrimsey]

Yes I did exactly that first. Current state is:

• External server (VPS1) and Dokploy server (VPS2)
• External registry added, specified VPS1
• Create application, Docker provider
• Specify private image - add username/password on the Provider options
• Works to deploy to Dokploy server, fails to pull when on external

I did manually login to ghcr.io on my external VPS (/home/root/.docker/config.json exists) when we solving the compose issue (which was resolved by changes in 0.9.4)