Skip to content

Commit 1ca89a1

Browse files
committed
docs: clarify network requirements for Dokploy in Docker Compose
- Added a note regarding the necessity of including `dokploy-network` in all services when not using Isolated Deployments to ensure connectivity. - Enhanced the documentation to provide clearer guidance on network configurations in Docker Compose setups.
1 parent 7ab0dc1 commit 1ca89a1

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

apps/docs/content/docs/core/docker-compose/domains.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,7 @@ networks:
8585
**Important Notes:**
8686
8787
- If you don't add any domains through the UI and don't use [Isolated Deployments](/docs/core/docker-compose/utilities#isolated-deployments), your application will be deployed exactly as you specified in your original Docker Compose file - no labels or network modifications will be added.
88+
- If you're not using [Isolated Deployments](/docs/core/docker-compose/utilities#isolated-deployments), Dokploy will add the `dokploy-network` to the service you selected, however you need to add `dokploy-network` to the other services to maintain connectivity.
8889
- The Preview Compose button is useful for verifying how Dokploy will modify your compose file before deployment.
8990
- All label generation and network configuration is handled automatically by Dokploy based on your domain settings.
9091

0 commit comments

Comments
 (0)