> > >> Assuming that: > 1) The kill old container task isn't supposed to be present in the second > example > 2) The snazzy/cyweb container is running a long running process > 3) Manually running docker's tools does something similar > > I think this behaviour is intended. > > This seems like we're just asking the docker module to guarantee that the > service is running. Not to restart the service. I think we need to be > explicit here that we aren't just saying "ensure service is running" but > are actually saying "restart the service, picking up a new version if > that's deployed". > > -Toshio >
Sorry I'm slow to understand Ansible. But the docker module is suppose to guarantee that the service is running, correct. Shouldn't it ensure that the VERSION of the service I specify in the playbook is running? How does ansible handle this for other applications besides docker? I will need to go look at that. Won't ansible let me say I want "version 1.0 of clock app", "version 1.5 of snogger app". And if the server has ".09 of clock app" and "1.0 of snogger app", it should change them to the new version, correct? tnx -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/fc4c9f3b-7e63-4c93-9f94-5e77e1b499af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
