container name with rolling update

[centralhardware]

I don't see any reason why applications with a specified container name can't support rolling updates; why not implement the same mechanism currently used for services, where a unique identifier is simply appended to the name?

[itsneeku]

+1, databases also don't follow the services' implementation

[gltched-usr]

+1, Atm you need to choose between beeing able to monitor the docker container (status pages) or have rolling updates, which is shit. Meaning every update causes short downtimes (especially because coolify first stops then pulls instead of first pulling and then stopping and starting (would be a smaller downtime)