how to force service using cutom network name

[delacosta456]

hi all
i am new to dokploy and would like to know how to force dokploy to create and use the a specified network name labeled in docker-compose.yml.
I noticed that event if i specified a network dokploy omit it and create another one for the service i am deploying.
For info i am using a self-hosted instance

Thanks

[dosubot[bot]]

Hi @delacosta456! I'm Dosu and I’m helping the dokploy team.

Dokploy intentionally manages networks for its services, which is why it overrides what you specify in your docker-compose.yml. By default, all services are attached to a shared network called dokploy-network so that Traefik can route traffic to them [1].

If you want to use a custom network, here's the workaround:

1. Manually create the network on your server first:

   docker network create --driver bridge --attachable my_custom_network

2. Reference it as an external network in your docker-compose.yml:

   services:
     myservice:
       image: your-image:latest
       networks:
         - my_custom_network
   
   networks:
     my_custom_network:
       external: true

Your services still need to be connected to dokploy-network for Traefik routing to work. If you're using multiple networks, you may also need to add this Traefik label manually to avoid 504 errors (cite:thread:060ba7cc):

labels:
  - "traefik.docker.network=dokploy-network"

Alternatively, you can look into the Isolated Deployment option in Dokploy's Advanced settings, which creates a separate network per application instead of using the shared dokploy-network. There are also Advanced Network settings available in the Advanced tab where you can configure network target, aliases, and driver options.

Let me know if you need more details on any of these approaches!

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[delacosta456]

ok it's clear. But the generated network name is too long