Open fipnooone opened 2 weeks ago
they are in the same network so you can use the container name of staging-project-mysql
they are in the same network so you can use the container name of staging-project-mysql
That's what i'm trying to do. When coolify starts an app, it generates unique container names, so i can't use the names from the original docker-compose.
@fipnooone you can use the service name, this doesn't change
@fipnooone you can use the service name, this doesn't change
🤦 thank you. But i'll keep this issue open, since COOLIFY_CONTAINER_NAME doesn't work as it should. Or maybe am i wrong here too?
@fipnooone thats the container name of the app, not the database, jsut use staging-project-mysql
Description
Created containers:
Docker inspect for node service show this env:
Docker inspect for mysql service:
Shouldn’t all containers have the same identifier? That is, 061119181951 in this case.
Minimal Reproduction (if possible, example repository)
docker-compose file:
Part of my env file:
Exception or Error
Version
v4.0.0-beta.323
Cloud?