Calling docker container restart <container> will somehow make the underlying docker commands used by ocurrent-deployer forget about it. Thus when upgrading the service associated with the container the old one will stick stick around and the new one will still be spawned.
Calling
docker container restart <container>will somehow make the underlying docker commands used by ocurrent-deployer forget about it. Thus when upgrading the service associated with the container the old one will stick stick around and the new one will still be spawned.