Darren Sisson
Darren Sisson
yes coolify doesnt really support multiple docker compose files if it just ran ```docker compose -f .$workdir$composeFile config --no-interpolate``` instead of just cat it would be fine i think (a...
can you show an image of what you are seeing, as all the connect to predefined network does is; it will add the containers to the coolify network, it does...
Can you paste or link to the compose file you are using
@Forceres can you check /horizon make sure queues are empty then run the following in a terminal on the vps and leave open ``` docker events -f 'type=network' ``` then...
@Forceres if you are trying to connect to this service from another compose, you need to connect both to the same docker network so either define your own network first,...
@Forceres the only thing it does, is connect the container to coolify network, nothing more if it's there then the issue is elsewhere, what is the contents of the prometheus...
I think you have mis understood what the option means. Maybe it is poor wording, but it means connect to docker network named coolify So if all your services are...
@Koliham those logs show you trying to connect to service called postgres Unfortunately coolify-db service name is also called postgres and is in coolify network This ip is returned first...
they are in the same network so you can use the container name of staging-project-mysql
@fipnooone you can use the service name, this doesn't change