-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old service containers aren't removed after docker service update "renaming" #24670
Comments
I think this is a duplicate of #24394, the difference being that this issue isn't about "faulty" containers. Can you try updating the |
Hi. I'm sorry. Nevertheless, after running the "renaming" command, old containers can't be removed using "service rm", because cluster doesn't exists anymore, and "docker rm" must be used. PS: --task-history-limit didn't seem to solve anything |
The reason you were not able to remove the old service, is that there is no old service; the service was renamed, so it's still the same service, only using a different name. For example:
You can remove all tasks/containers by removing the service using the new name:
|
Hi
We are running a service (logstash) which loads the configuration files at startup:
The containers are started and visible with docker ps -a
After testing some changes, we would like to have a rolling update without downtime.
To do it, I was trying to do:
If I understood correctly, this should replace each container with the new configuration.
Instead of that, docker ps -a is showing both of them: logstash-blue running and logstash-green stopped, which IMHO shouldn't happen.
Furthermore, I'm not able to remove old service using docker service rm logstash-blue (which makes sense if service is renamed).
Regards
The text was updated successfully, but these errors were encountered: