OK - after some discussion, it turns out that if the docker daemon is restarted, all the containers it manages get restarted as well - which sucks from a maintainability perspective BUT its how it is right now.
I still think there is an issue going from 0.9 -> 1.0 which is not this problem - waiting on upstream response.
OK - after some discussion, it turns out that if the docker daemon is restarted, all the containers it manages get restarted as well - which sucks from a maintainability perspective BUT its how it is right now.
I still think there is an issue going from 0.9 -> 1.0 which is not this problem - waiting on upstream response.