Zero-Downtime deployment

[AndyMik90]

For more production ready / production apps, zero-downtime deployments is a very nice feature to have (in my eyes a must).

Should not be to much of work to implement something with the current Traefik / Docker compose setup that Coolify has; found this nice guide on structuring it as a blue-green deployment strategy:
https://www.maxcountryman.com/articles/zero-downtime-deployments-with-docker-compose

[KaelWD]

Looks like it should be doable with --scale too: https://github.com/wowu/docker-rollout

[franciscobmacedo]

docker-rollout requires that the container can't have container_name which coolify automatically assigns, so I don't think it's a possibility?

[AndyMik90]

Maybe if this is not something that will be in Coolify natively, there could be some documentation how users can set it up for themselves with the proxy in Coolify? @andrasbacsai @peaklabs-dev

[ghost]

It's definitely possible because you can do it with normal docker, and since coolify uses docker then they should be able to added it, not sure why it's not in by default but it will be nice once its added.

[imankeeth]

+1

[mattaiod]

+1, you are amazing, please do that for the world ASAP. Thank you very much

[AndyMik90]

Any comments or feedback regarding this one @peaklabs-dev @andrasbacsai ?

[franciscobmacedo]

Did you made it work in a somewhat straightforward way? Wondering if you have any tips on how to set this up

[AndyMik90]

@franciscobmacedo myself have not had the time to set it up.

[roshanjonah]

+1

[AndyMik90]

@peaklabs-dev @andrasbacsai This could be a done quite easily as long as persistent storage is left out of the equation.

[djsisson]

you can switch to swarm mode, then this is handled automatically by docker

[luco]

@djsisson Any tips on how doing it?

[KaelWD]

@djsisson #3798

[djsisson]

@KaelWD you need to pre set it up

[luco]

@andrasbacsai @peaklabs-dev Thoughts?

[yes-oo]

any updates ? any ideas , this is what holding me back to launch my website with coolify

[SindelarPetr]

I would say this is the feature which would stop a lot of production projects from launching using Coolify. In my job, it was normal for Java or Python services to take take up to 30s to start.

On Kubernetes it was no big deal, because it supports zero downtime deployments out of the box.

I still think Coolify is still better alternative than Kubernetes for most of the non-enterprise projects. But this feature would allow software architects to explain the value of it to the necessary stakeholders.

[oribenez]

I think that also using dockerfile to start the container you dont have zero downtime deployment.
In my apps we have ~10 sec of downtime

[djsisson]

@oribenez as long as you don't have fixed ports, container name or ip, then the old container isn't stopped till after the new ones are up running and are healthy
so there should be no downtime

[oribenez]

@oribenez as long as you don't have fixed ports, container name or ip, then the old container isn't stopped till after the new ones are up running and are healthy

so there should be no downtime

Tnx for your quick reply.
That is strange cause i have ports on expose.
Maybe it is because i switched to caddy proxy?

[luco]

@djsisson How can we do it without exposing ports?

[oribenez]

@djsisson How can we do it without exposing ports?

Instead of port expose you can use the ports mapping solution.

[acoard]

So what's the status of zero downtime deployment and rolling updates? I see the documentation only refers to losing rolling updates if you do use port mappings. But the comments in this thread by @djsisson and @oribenez (thanks for helping out on this btw!) seem to imply you lose it if you don't use port mappings.

Additionally, the port expose seems like a required value. If I try to do what @oribenez proposes, not using port expose, the form validation blocks me. Am I doing something wrong? I'm using the nix build here, but happy to switch to docker if it helps.

Loving Coolify so far, but zero-downtime deployments are a must, and I would hate to have to migrate off of coolify.

[tomocrafter]

maybe this documentation is talking about Rolling Updates of Coolify itself: https://coolify.io/docs/knowledge-base/rolling-updates.

[garraflavatra]

No, that doc is about rolling updating your application. Make sure you have a healthcheck configured in order for rolling updates to work.

[grdevd]

@garraflavatra The problem exists when using Docker Compose. Even having healthchecks in the docker compose file and NOT using container name, during a deployment when the Docker file gets downloaded, the application shows

no available server

and this can take up to 1-2 minutes where the application is down.

On other platforms (like Digital Ocean), the container is replaced after starting and we have no downtime.

We have this problem with missing rolling updates with the following docker compose file:

version: "4"
services:
  client:
      image: "<docker image>"
      pull_policy: always
      environment:
          ...
      restart: unless-stopped
      expose:
        - "3000"
      healthcheck:
        test:
            - CMD-SHELL
            - 'curl -s -X GET -f http://localhost:3000/ > /dev/null || wget -q -O- http://localhost:3000/ > /dev/null || exit 1'
        interval: 10s
        timeout: 5s
        retries: 10
        start_period: 10s
  server:
      image: "<docker image>"
      pull_policy: always
      environment:
          ...
      restart: unless-stopped
      expose:
        - "1337"
      healthcheck:
        test:
            - CMD-SHELL
            - 'curl -s -X GET -f http://localhost:1337/ > /dev/null || wget -q -O- http://localhost:1337/ > /dev/null || exit 1'
        interval: 10s
        timeout: 5s
        retries: 10
        start_period: 30s

[djsisson]

@grdevd for compose based deployments, all containers are stopped before starting the new ones, there is no rolling update for compose based deployments currently.
as a workaround you can split your compose up into individual services to get rolling updates tho

[grdevd]

@djsisson Thanks for the clarification. We have docker compose in this case, because the "app" consists of a client and a server and we have multiple customer deployments with just different configuration.

But is it basically possible to realize rolling updates with Docker Compose and is Coolify planning to support this (at some point)?

[abumostafa]

I tried all the suggested comments. once I enabled "Disable build cache". seems like it worked

[leonbeckert]

@andrasbacsai @peaklabs-dev Thoughts?

[AndyMik90]

@andrasbacsai @peaklabs-dev Could we get some official documentation/guidelines regarding zero downtime deployment? limitations, traefik vs caddy proxy etc.

[garraflavatra]

Hot off the press: https://coolify.io/docs/knowledge-base/rolling-updates

[oribenez]

I want to add more facts to this thread so you all can solve this problem:
Before: I had downtimes on deployments. My setup: self hosted with caddy proxy, coolify version was beta 396.
After: Zero downtime deployments. I've switched to Coolify cloud and using traefik proxy, and some of my apps use ports mapping, on coolify cloud I use latest beta version.
Hope this info will help you solve your problems.

[SegoviaDiego]

How do you keep using health checks for rolling updates while using ports mapping?

When I enable ports mapping, my health checks features get disabled.

[PringlePot]

It would still be great if this could be implemented on 1-app compose deployments. I use compose for env variables, and manual traefik management, and having no rolling updates is a shame since i have downtime.

[gltched-usr]

+1