{"action":"created","issue":{"url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/34","labels_url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/34/comments","events_url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/34/events","html_url":"https://github.com/gliderlabs/docker-consul/issues/34","id":48003898,"number":34,"title":"Add leave_on_terminate = true to the default consul configuration","user":{"login":"rocketraman","id":53049,"avatar_url":"https://avatars.githubusercontent.com/u/53049?v=3","gravatar_id":"","url":"https://api.github.com/users/rocketraman","html_url":"https://github.com/rocketraman","followers_url":"https://api.github.com/users/rocketraman/followers","following_url":"https://api.github.com/users/rocketraman/following{/other_user}","gists_url":"https://api.github.com/users/rocketraman/gists{/gist_id}","starred_url":"https://api.github.com/users/rocketraman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rocketraman/subscriptions","organizations_url":"https://api.github.com/users/rocketraman/orgs","repos_url":"https://api.github.com/users/rocketraman/repos","events_url":"https://api.github.com/users/rocketraman/events{/privacy}","received_events_url":"https://api.github.com/users/rocketraman/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2014-11-06T19:31:07Z","updated_at":"2015-08-04T00:02:25Z","closed_at":"2015-06-30T18:08:08Z","body":"When doing \"docker stop\" on a container, the consul process will receive a SIGTERM. However, the consul agent does not leave the cluster gracefully upon SIGTERM by default. This results in problems when the node is restarted because it is assigned a new IP address. This then triggers this bug: https://github.com/hashicorp/consul/issues/457.\r\n\r\nBy adding leave_on_terminate = true to the consul configuration in `/config/consul.json` a `docker stop` command would be treated by consul as a graceful shutdown of that agent."},"comment":{"url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/comments/127437518","html_url":"https://github.com/gliderlabs/docker-consul/issues/34#issuecomment-127437518","issue_url":"https://api.github.com/repos/gliderlabs/docker-consul/issues/34","id":127437518,"user":{"login":"progrium","id":647,"avatar_url":"https://avatars.githubusercontent.com/u/647?v=3","gravatar_id":"","url":"https://api.github.com/users/progrium","html_url":"https://github.com/progrium","followers_url":"https://api.github.com/users/progrium/followers","following_url":"https://api.github.com/users/progrium/following{/other_user}","gists_url":"https://api.github.com/users/progrium/gists{/gist_id}","starred_url":"https://api.github.com/users/progrium/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/progrium/subscriptions","organizations_url":"https://api.github.com/users/progrium/orgs","repos_url":"https://api.github.com/users/progrium/repos","events_url":"https://api.github.com/users/progrium/events{/privacy}","received_events_url":"https://api.github.com/users/progrium/received_events","type":"User","site_admin":false},"created_at":"2015-08-04T00:02:25Z","updated_at":"2015-08-04T00:02:25Z","body":"Ah. It was supposed to use consul-agent as a base, but I see it's not.\nCan't remember if there was a good reason for that. Either way you're\nright.\n\nOn Mon, Aug 3, 2015 at 5:39 PM, vince rosso <notifications@github.com>\nwrote:\n\n> Oh, I was looking at the server config. Is there a reason why it shouldn't\n> be in there as well?\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/gliderlabs/docker-consul/issues/34#issuecomment-127424424>\n> .\n>\n\n\n\n-- \nJeff Lindsay\nhttp://progrium.com\n"}}