How to connect a compose app to a database in the same project?

[dllabs]

I have a project my-project that contains a Postgres database called db, and a compose app.
Dokploy tells me the internal hostname of the database is, say, myproject-db-123456.

When I use that hostname in a container in the compose app, I get an error saying:
could not translate host name "myproject-db-123456" to address

The only way I've been able to get containers in the compose app to see the database is add a networks: dokploy-network option in docker-compose putting the containers on the dokploy-network that Dokploy creates when a domain is added to the compose app.

Given that dokploy-network is external-facing, I probably don't want to be doing that, do I? So what settings do I add to my docker-compose so they can see a database that has been set up in the same project? What network are databases on?

This is the docker-compose I use, with the dokploy-network added:

services:
       
  webserver:
    build:
      context: ./django
    image: predictions-master
    entrypoint: /entrypoints/webserver_entrypoint.sh
    volumes:
      - predictions_django_static:/usr/src/app/static
      - predictions_bash_history:/commandhistory
    expose:
      - '8000'
    env_file:
      - ./.env
    networks:
      - dokploy-network

  nginx:
    restart: always
    image: nginx:1.27.2-alpine
    volumes:
      - ./nginx/default.conf:/etc/nginx/conf.d/default.conf
      - predictions_django_static:/var/www/static
    depends_on:
      - webserver
    networks:
      - dokploy-network

volumes:
  predictions_django_static:
  predictions_bash_history:

[bobir01]

@dllabs Hi, i have same problem didnt you find out how to connect it, and even in compose project i cant open terminal to container

[izniburak]

I also have same issue...

[minrudev]

This is a question I am having now, just maybe on a more abstract layer. Lets say I have deployed my NextJs app through git. Everything is fine, then I chose CoachDB template and added to the project. So , what would be INTERNAL url link that I would be able programmatically call my database from the inside my NextJS application ?

[minrudev]

This is a question I am having now as well, just maybe on a more higher level. Lets say I have deployed my NextJs app through git. Everything is fine, then I chose CoachDB template and added to the project. So , what would be INTERNAL url link that I would be able programmatically call my database from the inside my NextJS application ?

[minrudev]

Ah, it seems the answer lies here: #992

[izniburak]

Yes, this is a way to handle this issue. But why we have to use expose a port and use external connection? I think we should connect any service from each others by using internal host name on same network...

I prepared a Dockerfile or docker-compose file and added dokploy-network for my services, but still I couldn't connect to DB or other services.

Dokploy needs improvements about this issue.

[Siumauricio]

The dedicated databases will always be on the dokploy-network so if you need to connect you have to join your other containers to that network

another idea could be to have the database in your docker-compose file, since we now support backups and restore it could be a solution to move it there.

there is a feature request to handle networking and so on, I haven't had time yet but I have it in mind.

[izniburak]

Actually, I tried to use dokploy-network in my docker-compose file but still I couldn't reach the DB services I created directly on my Dokploy project. The option about the creating services in our docker-compose file is good idea as well but, still I think this dokploy-network support should be checked and supported.

Thanks for your contributions!

[minrudev]

I think I know what problem you're facing and the solution is rather the simple. As dokplay works a Kubernetes cluster, the DNS and domain name works differently inside the network. Lets say I have NextJS app and I chose to use CouchDB template for my project. You add it to dokploy-network, you can skip of exposing ports, just make sure you map those on the container (compose file) and the url will be docker image service name. Basically I am able to ping/curl from my NextJS container couchdb using url: http://couchdb:port. So internal url becomes: http://servicename:port Tested other servises/db , works the same. If you want to expose your port, just expose it, delete trafik url, block ports on your VPS server, add A alias for your domain provider and map that subdomain with your service/template. And you have working inside URL's and secure access from outside. Hope this helps.

[izniburak]

Thanks for detailed informations. I'm very appreciated that. I'll try something again under this informations. Probably, my main problem is related with docker projects.. Let me explain:

I prepared a docker-compose file for my project. I added app container for laravel project, pma container for PhpMyadmin, and worker container for a golang project. I try to deploy this docker-compose via Dokploy. And also, I added dokploy-network to all containers in docker-compose file. After that, I deployed a database service directly in Dokploy project, not in docker-compose. DB service deployeed successfully, and give me a internal host name like: lara-dbserver-a17bk1. But, I couldn't reach this database from my containers I created them in docker-compose file. Laravel project does not connect to database.

If I don't use docker-compose or Dockerfile for a service/deployment, I have no issue as you said. For example, I try to deploy NextJS or Golang projects directly from Github or similar services, or zip file, there is no issue. But if I use docker env for a service, these services have issues to connect other services which created from Dokploy.