From 1ca89a17dd912e0346933aaf5c59d733aeeb6eb6 Mon Sep 17 00:00:00 2001 From: Mauricio Siu Date: Tue, 9 Dec 2025 16:54:42 -0600 Subject: [PATCH] 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. --- apps/docs/content/docs/core/docker-compose/domains.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/apps/docs/content/docs/core/docker-compose/domains.mdx b/apps/docs/content/docs/core/docker-compose/domains.mdx index b7b3827..577b949 100644 --- a/apps/docs/content/docs/core/docker-compose/domains.mdx +++ b/apps/docs/content/docs/core/docker-compose/domains.mdx @@ -85,6 +85,7 @@ networks: **Important Notes:** - 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. +- 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. - The Preview Compose button is useful for verifying how Dokploy will modify your compose file before deployment. - All label generation and network configuration is handled automatically by Dokploy based on your domain settings.