To Reproduce
Preview deployments do not inherit the application's configured build server and build registry.
The regular application is configured with:
- custom build server
- private Harbor build registry
- Docker Swarm deployment cluster
Regular deployments build on the configured build server and push their image to Harbor. Preview deployments instead build on the application's deployment server and create a local-only image.
Current vs. Expected behavior
Current behavior
The preview build log ends with:
naming to docker.io/library/preview-testing-app-zwn41e-rp4jt8:latest
unpacking to docker.io/library/preview-testing-app-zwn41e-rp4jt8:latest
No registry login, tag or push is performed.
When Docker Swarm schedules the preview service on another node, the deployment fails with:
pull access denied for preview-testing-app-zwn41e-rp4jt8
repository does not exist or may require 'docker login'
The preview implementation currently explicitly sets application.buildRegistry, application.registry and application.rollbackRegistry to null. It also executes the build using application.serverId instead of application.buildServerId || application.serverId.
Expected behavior
Preview deployments should:
- Use the configured build server when present.
- Push the preview image to the configured build or cluster registry.
- Deploy the complete registry image reference to Docker Swarm.
- Pass the registry authentication when creating or updating the service.
- Store and clean up preview build logs and source files on the build server.
Provide environment information
Dokploy: v0.29.12
Docker Swarm with multiple nodes
External build server
Private Harbor registry
GitHub preview deployments
Which area(s) are affected? (Select all that apply)
Application, Docker
Are you deploying the applications where Dokploy is installed or on a remote server?
Both
Additional context
No response
Will you send a PR to fix it?
Yes
To Reproduce
Preview deployments do not inherit the application's configured build server and build registry.
The regular application is configured with:
Regular deployments build on the configured build server and push their image to Harbor. Preview deployments instead build on the application's deployment server and create a local-only image.
Current vs. Expected behavior
Current behavior
The preview build log ends with:
No registry login, tag or push is performed.
When Docker Swarm schedules the preview service on another node, the deployment fails with:
The preview implementation currently explicitly sets
application.buildRegistry,application.registryandapplication.rollbackRegistryto null. It also executes the build usingapplication.serverIdinstead ofapplication.buildServerId || application.serverId.Expected behavior
Preview deployments should:
Provide environment information
Which area(s) are affected? (Select all that apply)
Application, Docker
Are you deploying the applications where Dokploy is installed or on a remote server?
Both
Additional context
No response
Will you send a PR to fix it?
Yes