Open chrisbecke opened 4 months ago
services: my: image: 'nginx:latest' deploy: replicas: 3 container_name: my_container_1 deploy: replicas: 3 container_name: my_container_2 deploy: replicas: 3 container_name: my_container_3
Interested!
To resolve this issue, you need to ensure that each replica has a unique container name. You can achieve this by using the container_name option in your service configuration. Here's an example of how you can modify your Docker Compose file:
services: my: image: 'nginx:latest' deploy: replicas: 3 container_name: my_container_1 deploy: replicas: 3 container_name: my_container_2 deploy: replicas: 3 container_name: my_container_3
@Aniketh999 Sorry I somehow can't get this to work with your answer. Complains about duplicate "deploy:" What am I getting wrong? Would you mind posting a properly formatted example? Thanks!
Would be interesting to see if the same happens with a raw Docker Compose
The problem is inherent to coolify generating the container names and not knowing about replicas. So rather a feature than a bug :-).
I can get by with this workaround:
services:
worker-1: &worker
image: vanwittlaer/some-image:latest
restart: unless-stopped
...
worker-2: *worker
worker-3: *worker
The problem is inherent to coolify generating the container names and not knowing about replicas. So rather a feature than a bug :-).
I can get by with this workaround:
services: worker-1: &worker image: vanwittlaer/some-image:latest restart: unless-stopped ... worker-2: *worker worker-3: *worker
Smart! Unfortunately it might only solve half the problem, not having real replica prevents the rolling update features, meaning the service will experience down-time at each update.
Description
It is not possible to deploy Docker compose files with "replicas:" other than 1.
Minimal Reproduction (if possible, example repository)
Create a Docker Compose resource and attach the following compose.yaml
Exception or Error
Version
v4.0.0-beta.270