[Bug]: Rolling update causes 502 Bad Gateway

[garraflavatra]

Error Message and Logs

Docker based webservices (from private repo) are not available from the moment the deployment log says "Rolling update started" until the moment when the rolling update is reported to have been completed.

Steps to Reproduce

Trigger a redeploy using the redeploy button and hit Ctrl+R repeatedly in a browser window with the website that is being redeployed. It will work fine until the moment the rolling update starts; it will display a 502 error then. When the rolling update is completed, it is back up again.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

Unfortunately I cannot test it with the default Traefik setup now; I'm using a custom proxy image based on Caddy. I doubt this is a problem with Caddy. Or may this be related to #3706 with Coolify not being able to patch Caddy's configuration?

ARG CADDY_VERSION=2.8.4
FROM caddy:${CADDY_VERSION}-builder AS builder

RUN xcaddy build \
    --with github.com/lucaslorentz/caddy-docker-proxy/v2 \
    --with github.com/caddyserver/[email protected] \
    --with github.com/caddy-dns/[email protected]

FROM alpine:3.17

EXPOSE 80 443 2019
ENV XDG_CONFIG_HOME /config
ENV XDG_DATA_HOME /data

RUN apk add -U --no-cache ca-certificates curl

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

ENTRYPOINT ["/usr/bin/caddy"]
CMD ["docker-proxy"]