Utilities
Utilities for your Docker Compose application
Dokploy provides a set of utilities to enhance your Docker Compose application deployment experience.
Isolated Deployments
All open source templates come with this feature enabled by default.
This feature allows you to deploy your application in a separate network, isolated from other applications. This isolation is particularly useful when you need to deploy multiple instances of the same application.
For example, if you want to deploy two WordPress instances, you would typically encounter service naming conflicts since they share the same network (dokploy-network). Docker doesn't allow services with identical names in the same network. Consider this typical WordPress service:
services:
wordpress:
image: wordpress:latest
ports:
- "80"
When Isolated Deployments is enabled, Dokploy will:
- Create a network based on your
appNameand associate it with each service in your compose file - Add the network to every service in your compose file
- Connect the Traefik load balancer to this isolated network, maintaining service isolation while ensuring proper routing
When using this feature, you don't need to explicitly define dokploy-network in your networks section, as isolation is handled automatically.
Important: Installation Type Considerations
If you're using a custom installation that replaces the standalone Traefik container with a Docker service (see Manual Installation), be aware of the following risks:
-
System Restart Issues: If your system restarts, your services may lose their network references to Traefik. This happens because Docker Swarm changes network references after a restart, which can cause connectivity issues between your services and Traefik.
-
Manual Redeployment Required: After a system restart, you may need to manually redeploy your Docker Compose applications to restore network connectivity, which can be tedious and time-consuming.
-
Reference: For more details about this issue, see GitHub Issue #1004.
Recommended Approach: If you use the official installation or manual installation with the standalone Traefik container, you won't experience these issues. Your services should start normally after a system restart without requiring manual intervention.